Bug#460177: update-grub updates menu.lst with incorrect bootdevice

[Chris Knadle]

Thomas:

   This may be clear already, but in case it's not I wanted to give you a more 
detailed explanation -- the problem was that your original menu.lst file was 
set to have update-grub use hda6 as the boot device.  Specifically, this 
section:

   ## ## Start Default Options ##
   ## default kernel options
   ## default kernel options for automagic boot options
   ## If you want special options for specific kernels use kopt_x_y_z
   ## where x.y.z is kernel version. Minor versions can be omitted.
   ## e.g. kopt=root=/dev/hda1 ro
   ##      kopt_2_6_8=root=/dev/hdc1 ro
   ##      kopt_2_6_8_2_686=root=/dev/hdc2 ro
   # kopt=root=/dev/hde6 ro

Now, I know that that last line above LOOKS like a COMMENT, but that is also 
actually a SETTING used by update-grub to know what the boot device and mount 
options are that it should use for making the boot menu entries.

Anyway I hope that helps.

   -- Chris

-- 

Chris Knadle
Chris.Knadle at coredump.us
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
Url : http://lists.alioth.debian.org/pipermail/pkg-grub-devel/attachments/20080203/b0addf84/attachment.pgp