[Bug 429606] Re: menu.lst mess

[dino99]

outdated report & no more maintained distro; please send a new one if
that issue still exist (using ubuntu-bug)

** Changed in: grub (Ubuntu)
       Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to grub in Ubuntu.
https://bugs.launchpad.net/bugs/429606

Title:
  menu.lst mess

Status in grub package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: grub

  I always have two installations on my pc, one is the last ubuntu stable, the other one is ubuntu developping, to manage the two installations I have separated the /boot, it is in /sda1.
  The last I installed is obviously karmic koala that ships grub 2. When I finished to install everything was fine, karmic booted and I enjoyed the new ubuntu release, but when I tried to boot the stable (jaunty) I got a grub error.
  As I know well the trick I gone directly to the menu.lst and I found it messed up by the installer: all the uuid in the jaunty lines was changed according to the uuid of the new installation ...
  This is an old trick, always grub has done that mess, but I hoped that grub 2 would have fixed that!
  Up to jaunty, at least, the updater lets you to choose if it has to change the menu.lst automatically or not (I always say NOT!), but in grub 2 there is not that option.

  Is it so hard that the grub updater reads the old menu.lst lines and
  rewrite them without any change in the new menu.lst, instead of
  blindly read the content of /boot and rewrite the menu.lst assigning
  arbitray uuids?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub/+bug/429606/+subscriptions