| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 48802 | 2004-09-01 10:16:00 | Yoper Installation | Murray P (44) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 267979 | 2004-09-02 04:40:00 | `The simplest way to save the MBR is to (as root): dd if=/dev/hda of=savedmbr.dat bs=512 count=1 Then copy the file it produces to a floppy. That saves the whole sector, which includes the bootstrap, and the partition table. To replace it, dd if=savembr.dat of=/dev/hda . You can do all sorts of clever things like replacing just the bootstrap, or just the partition table by using "bs=1" and "count=446" or "skip=446". e.g. dd if=savedmbr.dat of=/dev/hda bs=1 count=446 |
Graham L (2) | ||
| 267980 | 2004-09-02 05:16:00 | LOL - And again, Graham has a nice easy way of doing it... Better than mucking about with Partimage etc :-) Let us know how you get on Murray, it shouldnt be too hard. Just clear the MBR before you get started and Lilo will install nicely! Chill. |
Chilling_Silence (9) | ||
| 267981 | 2004-09-02 05:46:00 | Of course, any saved sector such as this can cause serious problems if it's not kept up to date. If you change the partitioning, then restore an old table, there are certain to be tears before bedtime. You also need a way to do the restore ... a live CD version of Linux would be the easiest. ( Sometimes it's tricky to access files on MSDOS floppies from a rescue disk). Of course there's a "real programmer's" technique ... DOS and DEBUG. :D |
Graham L (2) | ||
| 267982 | 2004-09-02 13:04:00 | WOOOOO HOOOOOO :D :D :D :D :D :D :D :D :D :D :D :D :D Please excuse the totally immature hollering and stupid grinning, most unseemly of me . YEE Haa ;) I'm in and I'm blo*dy pleased with myself . Win 2k is still there and, Mepis I think but, most importantly I have an MBR and a boot loader which I didn't have for much of the night . Cough!! slight fib there, Mepis no longer has a boot loader but Yoper and 2k do . And Yoper's where it's at, at the mo . Cheers Murray P Yeah ok, but it's a big deal to me, especially when I couldn't boot any of the OS's, nada, zilch, broken . Then, at first, I couldn't nix the bits that were left to let me rebuild it . |
Murray P (44) | ||
| 267983 | 2004-09-02 13:24:00 | You should be able to copy the kernel files for Mepis into the /boot of Yoper..... Then edit /etc/lilo.conf to suit :-) Good to hear :-) First impressions of Yoper? Chill. |
Chilling_Silence (9) | ||
| 267984 | 2004-09-02 13:40:00 | Handsome wee OS :x Haven't had a good cruise around yet. Everything works as I set it up though. I was a bit worried about the nForce chipset which is what stopped me about a year ago, smooth as though, straight on the net and poped in here. I managed to back up the MBR from Mepis but on retrieval found it to be corrupted, something about invalid parameters in the table, I think?? that is what was written within the file, the rest was junk. Couldn't even fix it booting to the 2k CD, long story. I have no doubt I'll get back into Mepis with a bit more knowledge as a bonus at the end of it all :) Cheers Murray P |
Murray P (44) | ||
| 267985 | 2004-09-03 11:57:00 | Hi Murray Glad you like Yoper :D > I have no doubt I'll get back into Mepis with a bit more knowledge as a bonus at the end of it all As Chill mentioned, this is quite easy to achieve by copying over the kernel files from the Mepis /boot partition. I can give you some instructions if you like? Well you might of figured this out from Chill's earlier instructions anyway, but just in case ... 1. Find out what partition Mepis / is. fdisk -l will give you the partition details. 2. Make a mount point for Mepis under /mnt mkdir /mnt/mepis 3. Mount the partiton using the partition details for the Mepis / mount /dev/hdXX /mnt/mepis 4. Open up the Super User Mode File Manager (found under System) and browse off to /mnt/mepis - you should be able to view Mepis /. With the File Manager, open up a new tab and go to Yoper's /boot. Copy from Mepis /boot the kernel initrd file to Yoper's /boot. You can rename that file to initrd-mepis so that it is easily differentiated from Yoper's initrd file. Also copy over the vmlinuz to Yoper's /boot. Again rename it to vmlinuz-mepis. 5. Now to hack lilo.conf. Go to /etc/lilo.conf and add to the bottom: image=/boot/vmlinuz-mepis label=Mepis read-only root=/dev/hdXX <--- put Mepis / partition here append = "splash=silent " initrd=/boot/initrd-mepis 6. Open up a root console and enter in /sbin/lilo to re-run lilo so that it will recognise the new changes. 7. Reboot the machine and select "mepis" off the boot menu, and *hopefully* you will get Mepis loading :D |
Jen C (20) | ||
| 267986 | 2004-09-04 14:06:00 | Ya, Jen, I've been having a look at mounting all the partitions, only root and swap out of 10 . Got instructions off the net to edit /etc/fstab, starting with hda1 (win) but ran into permission trouble while I was root?? so will go back and RTFM . In Mepis all the drives and partitions were already listed in Kwikdisk so mounting and browsing was all point & click . This time I have to point it in the right direction first, all the info is there it's just a matter of putting it in the right place with the right commands which, might seem obvious but took me a while looning around in directories and looking things up . The documentation is fairly thin so it's off to the net then back again . I'll get there though if I don't try to go too fast . GL, I'll try to adhere to the straight ahead approach, as Chill puts it, whenever I can . It seems to me that this will involve less pointing and a little more doing with the result that I'm starting to appreciate the simplicity and elegance of this method of communicating my desires rather than the remote, uninvolved, approach I've been used to in windows and to an extent in Mepis . I'ts just a bit of a battle to get this poor head around at times, one cog at the time the gears are starting to mesh and turn . Thanks you all for your help :) Cheers Murray P |
Murray P (44) | ||
| 267987 | 2004-09-04 15:55:00 | The fstab isnt too hard.... /dev/hdaX = the devfs node entry /mnt/hdaX = the mountpoint for this device auto = File-system Type (vfat, msdos, smbfs, captive-ntfs, ext3, reiser4 etc etc) umask=000,users,noauto = Give all users RW permissions, Allow anybody to mount/unmount it, dont mount it at boot 0 0 = FS checking at boot etc. I just set it to 0 0 normally, but in yoper my / reiser4fs is 1 1. All other partitions I make are 0 0 however :-) Does this help in any way? Cheers Chill. |
Chilling_Silence (9) | ||
| 267988 | 2004-09-04 16:07:00 | Bleep, I was about to go to bed, where did you spring from? Yes I pretty much did that with the 0 0 at the end, my reiser4 has the 1 1 as per yours but it wouldn't save my edit, it said I didn't have permission :_| Back to basics I think, should I be doing this as root (as I was) or SU, should I log in as root or just start a terminal session as root? Or as I suggested in my previous post, just go back and read up on permissions because it's pretty basic making things work in Linux. I'll pick this up tomorrow so no need to go into it now. Cheers Murray P |
Murray P (44) | ||
| 1 2 3 4 | |||||