Package: release-notes Severity: normal After upgrading from sarge to etch, users were invited to manually update some entries in /etc/kernel-img.conf (specifically, the postinst_hook and postrm_hook) as described in etch's /usr/share/doc/grub-doc/NEWS.Debian.
However, this was not totally obvious, and because the compatibility wrapper ensured that everything worked, I imagine there are quite a few systems where this was not done. It seems possible that such systems would break after the upgrade to lenny (although I haven't tested this). If it is known that they will not break, then please close this bug! (and accept my apologies). Otherwise, it might be helpful to add something like the following to the release notes, possibly at 4.1.1.2 (straight after 4.1.1.1 makes sure that you are on a suitable kernel) or 4.1.6 (straight after LILO issues). 4.1.1.2 Check grub's kernel installation hooks If you use GRUB as bootloader and previously upgraded to etch from an older release of debian, please verify that the hooks in /etc/kernel-img.conf have been updated from /sbin/update-grub to /usr/sbin/update-grub. The older path will cease to work after the upgrade to lenny. For more details, see /usr/share/doc/grub-doc/NEWS.Debian from the grub-doc package. I hope this helps! Best wishes and thanks for all your work on debian... -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-6-k7 Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
