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

[Stéphane Graber]

Attaching the debdiffs:
 - upstart: Remove any reference to friendly-recovery from rcS.conf
 - initramfs-tools: Add support for startup-event parameter (forwarded to init)
 - grub2: Replace "single" by "startup-event=recovery-mode"
 - friendly-recovery: Move from /usr to /lib, start from recovery-mode instead of single, split menu into read-only and read-write mode. See above for full changelog

** Summary changed:

- recovery mode mounts filesystems read-write rather than read-only
+ [UIFe] [FFe] recovery mode mounts filesystems read-write rather than read-only

-- 
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/575469

Title:
  [UIFe] [FFe] 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