Jonas Smedegaard a écrit :
> If you dislike the confusion of the many choices (and us package
maintainers disagreeing of what's best), then use the same as gets installed by default using a recent
debian-installer. On IBM-compatible x86 systems that means the bootloader "grub", the ramdisk-generator
"initramfs-tools", a kernel compiled and packaged by the Debian kernel team, and devices handled by udev.
My problem is that my box is running since March 2002 and the defaults weren't the same at this prehistorical time.
It has been apt-get'ed daily and rebooted many times following the successive kernels (2.2, 2.4, 2.6) an releases
(Potato, Woody, Sarge, Etch and now Lenny) , by the way this means that the debian upgrade system is working very well
to get through all those evolutions
As there was no hardware changes since the start, this means that the reboot problem I recently met is strongly linked
to the 2.6 kernel or at least to its install scripts which might have forgotten something in the upgrade process
when Maximilian says
most probably a missing lilo run.
I answer if lilo hadn't run it would be the upgrade script fault. But as written in comment #10 lilo had run :
You already have a LILO configuration in /etc/lilo.conf
Running boot loader as requested
Testing lilo.conf ...
Installing the partition boot sector...
Running /sbin/lilo ...
using lilo is masochistic, grub is the default since some time.
And as I just explained my box was running long before grub became the default. And I have enough problems for now
without testing another boot manager
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact email@example.com