On Tuesday 14 January 2003 12:25, you wrote: > "H.J.Bathoorn" <[EMAIL PROTECTED]> writes: > > First there's the original lilo.conf here with all the entries. > > The second is what it looked like after upgrading the 9.0 on /dev/hdd1. > > > > Note that there's no entry for 2.4.21-pre2.1mdk there. > > Leaving only the 'freeduc' and 'linux-NOOD' (nood=Dutch for rescue) entry > > bootable. > > On reboot (still defaulting to win4lin) naturally gives a nice mess=:o( > > i really must miss something. > > isn't /boot/vmlinuz a symlink to vmlinuz-2.4.21-pre2.1mdk? > and /boot/initrd.img a symlink to initrd-2.4.21-pre2.1mdk.img?
Just checked: They are indeed symlinked that way. Meaning I assumed too quickly: nothing's really wrong there except that leaving the default as it is (to "win4lin" in my case) makes it accident prone. I don't understand why the win4lin entry has changed it's init.rd from 2.4.19-16 to 2.4.18-6 though. Changing default to "linux" on reboot might be better. HarM
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
