In Manoj Srivastava's email, 10-05-2001: > >>"Danny" == Danny ter Haar <dth@trinity.hoho.nl> writes: > > Danny> Itai Zukerman <zukerman@math-hat.com> wrote: > >> lilo needs to be re-run after installing a new kernel, right? grub > >> doesn't? > Danny> correct, although for automatic reboot of new kernel, new config > Danny> lines need to added... > > That is not the case. kernel-package already allows you to > boot the latest kernel image without changing the lilo.conf > file, by manipulating a couple of symbolic links. > > manoj > -- > Vulcans never bluff. Spock, "The Doomsday Machine", stardate 4202.1 > Manoj Srivastava <srivasta@debian.org> <http://www.debian.org/%7Esrivasta/> > 1024R/C7261095 print CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E > 1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C Well, it does, and I like thew feature, but it's not entirely great. If you install a newer compile of the same kernel with make-kpkg, it overwrites your old kernel named the same version (so if you install 2.2.18-2, it'll overwrite /boot/vmlinuz-2.2.18 which was also in 2.2.18-1). This makes /vmlinuz and /vmlinuz.old point to the same kernel, which isn't all that useful when the new kernel breaks. I keep a 'failsafe' kernel in my lilo.conf which points to a default kernel just to be safe. It'd be nice to see make-kpkg use the version number in it's kernel name, like /boot/vmlinuz-2.2.18-1 and /boot/vmlinuz-2.2.18-2 -- that would make this work correctly, but might clutter up the /boot directory.. -- Michael Janssen - Jamuraa - janssen@cns.uni.edu - jamuraa@base0.net GPG Fingerprint: 87F1 92C4 44AA 4105 B1C4 EDEC D995 9620 C00E 9159
Attachment:
pgpfWk1kXntsb.pgp
Description: PGP signature