update-grub and kopt / groot lines

[Florian Zeitz]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Laurent - CyberSDF schrieb:
> Hello all,
> 
> First sorry for my poor english.
> 
> 
> On a laptop with a dua-boot (windows / Ubuntu) i made something like that :
> /dev/hda1 => Windows
> /dev/hda2 => /
> /dev/hda3 => swap
> 
> after somme time the size of hda3 was too small for the user, right there
> is much free place on hda1.
> 
> After partitionnement i have :
> /dev/hda1 => Windows
> /dev/hda2 => /home/user/data
> /dev/hda3 => /
> /dev/hda4 => swap
> 
> Of course i have edited my menu.lst to indicate the new location of my
> root and my kernel and all work fine.
> 
> But when a kernel update came, the menu.lst was regenerated with old
> values. So strange... Why this ?
> 
> After some research, quite simply, when update-grub is calling by the
> kernel update operation the two lines
> # kopt=root=/dev/hda3 ro
> # groot=(hd0,2)
> are interpreted whereas they are commented.
> 
> I think this is very awkward, and i suggest to modify this operation by
> interpreting them ONLY if the line is uncomment.
> 
> 
> 
Hy,
well first I should probably say this is not really appropriate for
ubuntu-devel.
This behaviour is intended and competeley sane IMHO. update-grub has to
get the information which device is the root device/which options to
pass to the kernel and where to write the bootloader from somewhere. As
a user who wants to change this is going to look in the menu.lst it is
the best place to put this information. The lines can't be uncommented,
because if they were grub would try to interpret them and fail.
The comments in the menu.lst also clearly state that what the kopt and
groot options are used for and how to use them. They also state, that
update-grub will modify the automagic kernel list that you edited.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (MingW32)

iD8DBQFE2K6b0JXcdjR+9YQRAhOAAJ4vQfcUtDMri2P+56wsx/gIgSs90QCfSKbQ
mi4XKTpZxtx8CyPN7CaGz6w=
=DCWy
-----END PGP SIGNATURE-----