On Thursday 10 March 2005 01:13 am, Mikkel L. Ellertson wrote: > > I tried it first, but lilo complained about 'no root partition found' > > Let me guess - the second copy of lilo is the one that complained, > right? If so, check your /etc/lilo.conf in Suse, and make sure it is > correct. Make sure you run lilo in Suse after you make any changes in > that copy of the config file. The thing you have to remember here is > that you will be using two separate lilo installs to boot Suse. The > version from Mandrake handles booting Mandrake, and Windows. To boot > Suse, it will hand control over to the Suse lilo install, and it will > handle booting Suse.
No, the one that complained is Mdk's lilo. That's why then I googled and found the way to 'load' Suse's lilo from Mdk by mounting the partition in Mdk. > As far as the Mandrake version of lilo knows, it could be booting any OS > when it uses the "other=/dev/hda10" entry. > Yes, that is why. I am surprised it even boots. If the old version of > the kernel and initial RAM disk were removed as part of the upgrade, > then the only reason it still boots is that the space they use on the > disk has not been overwritten by new data. > > The thing you have to understand about lilo is that it is really two > separate parts. The part you run from Linux understands the file system, > and configures things for the part that actually boots the system. The > part that boots the system does not understand the file system. All it > know is where the information it wants is located on the disk. You gave > it this information when you ran lilo in Linux. But if you make changes, > you have to run lilo again, to update this information. > > With the normal setup, this is not a problem. The package managers in > both Suse and Mandrake take care of running lilo for you when you update > the kernel. But, because you are using the Mandrake copy of lilo to boot > Suse, Yast updates the wrong version of lilo. Mandrake does not take > care of it, because it has no idea that you updated the kernel in Suse. > So you have to do it manually. > > I would spend the time getting the version of lilo on /dev/hda10 > working, and using the "other=/dev/hda10" option to boot Suse. Or I > would consider changing Mandrake to use Grub instead of Lilo. Grub does > understand file systems, so it would handle the kernel changing in Suse > better. You would still have to make sure and update the grub config > files when you change kernels, but at least if would warn you when you > break things. > > Now, if you want a real challenge, install one of the other boot manages > on the MBR, change Mandrake lilo so it installs to your root partition > instead of the MBR, and let the boot manager give you a menu for > Mandrake, Suse, or Windows. There are several options for free boot > managers on freshmeat, or you could go with something like System > Commander. > > Mikkel Thank you so much for the very detail explanation Mikkel. I really appreaciate it. Your explanation opens up a new understanding for me on Linux bootloader. I will surely experiment it on my spare pc. -- Fajar Priyanto | Reg'd Linux User #327841 | http://linux2.arinet.org 21:34:16 up 30 min, Mandrakelinux release 10.1 (Official) for i586 public key: https://www.arinet.org/fajar-pub.key
____________________________________________________ Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Join the Club : http://www.mandrakeclub.com ____________________________________________________
