Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
look at all reported bugs in a timely manner.
This was reported against a very old release so I'm going to close it.
If you still have the issue please
Just tested.
Karmic on sda5 with /boot/grub/grub.cfg
F12 on sda6 with /boot on sda9
update-grub created for F12:
set root=(hd0,9)
search ... UUID_of_sda9
linux /vmlinuz... root=/dev/sda6
Problem solved. Thanks.
However, the initrd line is not created. I also have CentOS on this box
and its
Please check if this still happens with newest grub2.
At least that it still appends /boot/ if you have a seperate /boot partition
should be fixed now in karmic.
--
update-grub generates an incorrect entry
https://bugs.launchpad.net/bugs/442631
You received this bug notification because you are
Just checking this report and noticed that my email to HankB was cut
off.
End of email: Ubuntu 9.04 (from 40_custom) and boot from Jaunty on
/dev/sda6.
One more thought (if you have enough space on /dev/sda6).
You could boot into Karmic, mount the two Jaunty partitions to, eg,
/mnt/sda5 and
Please see my thread at
http://ubuntuforums.org/showthread.php?p=8063611#post8063611 to
determine if this is the same bug. It caught my eye because I was
running Jaunty with a /boot partition and installation of the Karmic
beta with grub2 left my Jaunty install unbootable. (I have not figured
out
Please see my thread at
http://ubuntuforums.org/showthread.php?p=8063611#post8063611 to
determine if this is the same bug. It caught my eye because I was
running Jaunty with a /boot partition and installation of the Karmic
beta with grub2 left my Jaunty install unbootable. (I have not figured
