friendly-recovery violates the Linux Filesystem Hierarchy Standard
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
friendly-recovery (Ubuntu) |
Fix Released
|
Medium
|
Stéphane Graber | ||
newt (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: friendly-recovery
friendly-recovery uses files in /usr, but runs in single-user mode.
This is a violation of the Linux Filesystem Hierarchy Standard, which states that "The contents of the root filesystem must be adequate to boot, restore, recover, and/or repair the system." (See http://
friendly-recovery, due to the current install locations:
(1) prevents the system from booting in recovery mode if the /usr partition is corrupted.
(2) prevents /usr from being resized, as it can never be unmounted
I'm a fan of LVM, and found #2 a huge problem for me. A huge benefit of LVM is that it allows you to dynamically increase the size of partitions. This benefit is negated if you can't unmount some of your partitions due to software using it.
Related branches
Changed in friendly-recovery: | |
importance: | Undecided → Medium |
status: | New → Triaged |
Changed in newt (Ubuntu): | |
status: | New → Invalid |
My preference:
Instead of /usr/share, the recovery menu logic moves to /lib. Either whiptail needs to also move to /bin, or you need to fall-back to a shell-based solution if whiptail is unavailable (such as the partition not available).