I think either linux-boot-prober or update-grub need a fix. As far as I
remember, the point was that $mpoint/boot/grub/grub.cfg is not a
reliable source of information. However, if you can do `mount $DEVICE
$mpoint`, you can trust that $DEVICE correct, because the environment in
which update-grub
HOLY COW This bug was reported in 2010 AND STILL HAS NOT BEEN FIXED
! Totally unacceptable.
To make sure we have a common understanding. I have linux on partition
sda9 and "other" version of linux on partitions sda8, sdb8, and sdb9.
The menu entries for ALL the "other" linuxes all specify
The problem with this solution is, it is discarding most of the
information of os-prober, and instead is just enumerating the kernels &
initrds that are listed in /lib/modules. Now I haven't checked with many
distributions, but I know Ubuntu, Debian, OpenSUSE and RedHat is using
this same
Peter, have you tried to get this into upstream or at least into Debian?
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/508901
Title:
update-grub sets wrong root argument
To
This is fixed by applying this:
https://gist.github.com/pepa65/85d5fcd1e12bc6028501c746258ac8cf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/508901
Title:
update-grub sets wrong root argument
To
This is fixed by applying this:
https://gist.github.com/pepa65/85d5fcd1e12bc6028501c746258ac8cf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/508901
Title:
update-grub sets wrong root argument
To
I had a similar problem after copying all files from the root partition
/dev/sda1 to another partition /dev/sdb1 and trying to tell grub to boot
from there now.
I digged into problem a little bit...
When i run `update-grub` it runs each of the files in `/etc/grub.d/`, my linux
copy (Ubuntu in
Appears to be related to Bugs 392836, 462961, and 551790.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/508901
Title:
update-grub sets wrong root argument
--
ubuntu-bugs mailing list
Maybe this is related to bug 551790?
--
update-grub sets wrong root argument
https://bugs.launchpad.net/bugs/508901
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I agree, grub2 is a complete mess here and this problem looks closely
related to what I reported in bug 510824. I talked to the devs in #grub
about it, but unfortunately they don't seem to care about shipping a
quality product.
** Changed in: grub2 (Ubuntu)
Importance: Undecided = Medium
**
/etc/grub.d/30_os-prober uses os-prober to determine the parameters to
pass to linux. os-prober in turn looks at what is passed to the kernel
in that system's /boot/grub/grub.cfg. Since that system is a copy of the
main one, its grub.cfg has the main system's UUID for the root=
parameter.
That is
proficient with them = proficient with computers
--
update-grub sets wrong root argument
https://bugs.launchpad.net/bugs/508901
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Jordan, thank you for that explanation. I would say, that is way to
complicated for an ordinary user (I consider myself proficient with them
and would have to reread a couple of times to understand what it is you
want the user to do). This needs to be dumbed down so that it just
works and an
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/38009317/Dependencies.txt
** Attachment added: XsessionErrors.txt
http://launchpadlibrarian.net/38009318/XsessionErrors.txt
--
update-grub sets wrong root argument
https://bugs.launchpad.net/bugs/508901
You received this
14 matches
Mail list logo