GRUB_DISABLE_INITRD should imply GRUB_FORCE_PARTUUID
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
grub2 (Ubuntu) |
Triaged
|
High
|
Mathieu Trudel-Lapierre |
Bug Description
Currently, if you want to boot a Linux system without an initrd, you have to both set GRUB_DISABLE_
disabling initrd boot only works if your root filesystem is specified in a syntax
If GRUB knows the root device, it should be able to probe the partition uuid of it without having to ask.
If the root disk is specified in a format that is known to not be resolvable by the kernel (LABEL= or UUID=), and grub is not able to resolve this to a partition uuid at update-grub time, then GRUB_DISABLE_
However if grub is able to resolve it, then GRUB_DISABLE_
Changed in grub2 (Ubuntu): | |
assignee: | nobody → Canonical Foundations Team (canonical-foundations) |
milestone: | none → ubuntu-17.03 |
Changed in grub2 (Ubuntu): | |
assignee: | Canonical Foundations Team (canonical-foundations) → Mathieu Trudel-Lapierre (cyphermox) |
Moving to ubuntu-17.05 so it remains on my todo list, I'll get to it immediately after the zesty release.