On Wed, 13 Aug 2003 19:36:17 -0600 [EMAIL PROTECTED] (Bob Proulx) wrote: > > A longer answer is that writing a new boot block with the existing > > lilo.conf would simply re-write the current boot sector, which would > > boot the old kernel. > > Are we talking about the same question? At the point that the > question is asked if lilo should be run the new kernel is already > installed, the symlinks pointing to it, and running lilo will set up > the boot to go to the new kernel. > > I guess it all depends on what is in your existing lilo.conf file. > But if you are just doing the normal default Debian installed lilo.conf > file it should be fine.
I don't normally use lilo -- I use grub instead, so before I released my revision to the newbiedoc I installed the Woody base system on my trusty Toshiba and used that installation to test my procedures. When I got to the "install ... existing lilo.conf" question, if I answered yes rebooting the system when the script finished would boot the old kernel. Doing as I wrote would boot the new kernel. > I have noticed a bug in the kernel-image*.postinst script which does > not always get the /vmlinuz et al symlinks correct, leaving them > pointing to the old kernel. I tried debugging that problem but have > not closed to root cause yet so I have not reported it yet. I think > perhaps it failed to update your symlinks when you had the failure. > In that case you do need to correct the symlinks and run lilo again. > I only see this when I am going forward and backward while hacking a > new kernel. It normally works when just moving forward. > > > What you want to do is install a new boot block which refers to the new > > kernel you just compiled. > > Which should be the default. I don't like the symlinks thing anyway -- I would prefer to refer to a kernel by its full name (as grub does). I agree though, that installing a new boot block referring to the new kernel should be the default. > P.S. Let me second the review that your 'newbiedoc' is excellent. Thank you. If you can see ways to make it better please let me know. Kevin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
