[Bug 575469] Re: recovery mode mounts filesystems read-write rather than read-only

[Stéphane Graber]

Working on implementing option 2, I noticed that friendly-recovery depends on whiptail which is in /usr/bin.
We're not going to be moving whiptail and libnewt out of /usr this cycle but it's definitely something that should happen for next cycle (opening bug tasks for these two).

For now, friendly-recovery itself will be in /lib and will simply drop
to a root shell if /urs/bin/whiptail can't be accessed.

Whenever we move whiptail to /bin we should also make sure nothing
currently refers to it with an hardcoded path as friendly-recovery used
to do.

** Also affects: newt (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: newt (Ubuntu Oneiric)
       Status: New => Invalid

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

Title:
  recovery mode mounts filesystems read-write rather than read-only

Status in “friendly-recovery” package in Ubuntu:
  Confirmed
Status in “newt” package in Ubuntu:
  Invalid
Status in “friendly-recovery” source package in Oneiric:
  Confirmed
Status in “newt” source package in Oneiric:
  Invalid

Bug description:
  Binary package hint: friendly-recovery

  In recovery mode, filesystems should probably be mounted read-only,
  since pending any problems they can safely be remounted read-write,
  while the reverse is not necessarily true.  This means that operations
  such as fsck, badblocks, zerofree, etc. are not possible without
  having to use a boot CD, and ensuring that any additional binaries are
  compatible.  One should assume that booting into recovery mode is
  either deliberate or has come about because of a problem.

  f-r 0.2.10 on lucid/2.6.32-21-generic

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