Package: lilo Version: 1:22.8-7 Severity: important Hello,
When upgrading a 2.6.26 kernel, LILO is not run anymore, so the computer won't reboot properly if we forget to manually run LILO. It was working fine when upgrading 2.6.25 kernels, and LILO stopped being executed automatically only once I upgraded to the 2.6.26 kernel. Maybe it is a release candidate bug, because while it is easy to manually execute lilo after upgrading the kernel, forgeting to do so may lead to important problems with remote servers. At least, I think it should be a release goal if it is not already the case. I am not sure if this bug is in the LILO package itself, but if not you will certainly know very well to which package to reasign it. Thank you in advance, Simon Valiquette http://gulus.USherbrooke.ca -- Installed kernels: ii linux-image-2.6-686 2.6.26+17 ii linux-image-2.6.25-2-686 2.6.25-7 ii linux-image-2.6.25-2-686-bigmem 2.6.25-7 ii linux-image-2.6.25-2-vserver-686 2.6.25-7 ii linux-image-2.6.26-1-686 2.6.26-11 ii linux-image-2.6.26-1-vserver-686 2.6.26-11 ii linux-image-2.6.26-1-vserver-686-bigmem 2.6.26-11 ii linux-image-686 2.6.26+17 ii linux-image-vserver-686 2.6.26+17 ii linux-image-vserver-686-bigmem 2.6.26+17 -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-vserver-686-bigmem (SMP w/2 CPU cores) Locale: LANG=fr_CA, LC_CTYPE=fr_CA (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/dash Versions of packages lilo depends on: ii debconf [debconf-2.0] 1.5.24 Debian configuration management sy ii libc6 2.7-16 GNU C Library: Shared libraries ii libdevmapper1.02.1 2:1.02.27-4 The Linux Kernel Device Mapper use ii mbr 1.1.10-1 Master Boot Record for IBM-PC comp lilo recommends no packages. Versions of packages lilo suggests: ii lilo-doc 1:22.8-7 Documentation for LILO (LInux LOad -- debconf information: liloconfig/fstab_broken: * liloconfig/banner: liloconfig/liloconf_incompatible: lilo/bad_bitmap: liloconfig/use_lba32: true lilo/upgrade: * liloconfig/liloconf_exists: liloconfig/configuring_base: liloconfig/use_current_lilo: false * lilo/runme: true liloconfig/wipe_old_liloconf: true * liloconfig/instruction: liloconfig/activate_error: * liloconfig/select_bitmap: /boot/debianlilo.bmp liloconfig/lilo_error: * lilo/new-config: liloconfig/odd_fstab: * liloconfig/install_from_root_device: true * liloconfig/make_active_partition: true liloconfig/maintitle: liloconfig/mbr_error: * liloconfig/lilo_warning: * liloconfig/install_mbr: true liloconfig/no_changes: * lilo/add_large_memory: false -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
