Package: grub Version: 0.97-10 Followup-For: Bug #370644 Hi!
This patch fixes the issue for instant. But there is still work to be done till this lockold feature does it's job right. What if the default entry is not the first one like with "default = 2"? line 935-936: # do not lockold for the first entry [ $counter -eq 1 ] && do_lockold=false Should memtest be locked by lockold? BSD kernels lack the lockold feature at all. Here is the (paranoic) workaround enabling lockold for memtest and bsd even if they might be the default: --- update-grub 2006-06-07 11:52:19.000000000 +0200 +++ update-grub 2006-06-07 12:04:24.000000000 +0200 @@ -884,7 +884,7 @@ else kernel=/boot/loader fi - write_kernel_entry "" "" "" "$grub_root_device" "$kernel" "" "" "" "true" + write_kernel_entry "" "" "" "$grub_root_device" "$kernel" "" "" "" "true" "$lockold" ;; esac @@ -967,7 +967,7 @@ echo "Found kernel: $kernel" >&2 write_kernel_entry "$kernelVersion" "" "" "$grub_root_device" \ - "$kernel" "$currentOpt" "" "$initrd" "false" + "$kernel" "$currentOpt" "" "$initrd" "false" "$lockold" fi done fi Hope this helps. Regards, Christopher -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/dash Kernel: Linux 2.6.16.20 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]