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.On Wednesday 09 March 2005 11:22 am, Mikkel L. Ellertson wrote:
other=/dev/hda10 lable="Suse92"
When you pick this option, it will transfere control over to the new version of lilo.
I tried it first, but lilo complained about 'no root partition found'
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 way you have it set up, if you update the kernel in Suse, you then have to boot Mandrake, update /etc/lilo.conf, and run lilo before you can boot the new kernel in Suse. Also, if you want to have more then one kernel in Suse, you will have to add the entries in the Mandrake copy of lilo.conf, and run lilo from Mandrake. Also, if you wipe out the boot partition in Mandrake, you will not be able to boot Suse from the hard drive.
Ah interesting, no wonder when I update my Suse kernel with Yast Online Update, it gave me lots of error when rebooting about can't find /lib/modules..
Many thanks Mikkel :) I hope Mdk10.2 will be much better than Suse92.
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 --
Do not meddle in the affairs of dragons, for you are crunchy and taste good with Ketchup!
____________________________________________________ Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Join the Club : http://www.mandrakeclub.com ____________________________________________________
