[Bug 234409] Re: friendly-recovery violates the Linux Filesystem Hierarchy Standard

[Launchpad Bug Tracker]

This bug was fixed in the package friendly-recovery - 0.2.13

---------------
friendly-recovery (0.2.13) oneiric; urgency=low

  * Move everything to /lib/recovery-mode/ (LP: #234409)
  * Don't use the fullpath to whiptail
  * Add new init script starting on recovery-mode (LP: #459376)
  * If whiptail can't be found, just start sulogin
  * Add a script to start mountall (remount everything read/write)
    (LP: #575469, LP: #651782)
  * Export READONLY to all scripts so they can test on the read/write state
  * Disable most scripts when the system is read only
  * Change file system check to happen when remount is called
  * Wait after all scripts returning output so the user can read it
  * Add postinst script to move any existing script to /lib/recovery-mode
    and make /usr/share/recovery-mode a symlink
  * Mark as breaking on older grub2, upstart and initramfs-tools
  * Small packaging refresh:
    - Bump standard to 3.9.2, no change needed
    - Drop simple patchsys (no patches)
    - No need to depend on bash (essential package)
    - Add ${misc:Depends} to dependencies
 -- Stephane Graber <stgraber at ubuntu.com>   Wed, 07 Sep 2011 20:18:53 -0400

** Changed in: friendly-recovery (Ubuntu)
       Status: Triaged => Fix Released

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

Title:
  friendly-recovery violates the Linux Filesystem Hierarchy Standard

Status in “friendly-recovery” package in Ubuntu:
  Fix Released
Status in “newt” package in Ubuntu:
  New

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://www.pathname.com/fhs/pub/fhs-2.3.html#PURPOSE2 )

  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/234409/+subscriptions