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

[Stéphane Graber]

Feature Freeze exception:
 - Adds a new feature to initramfs-tools and use it in grub2 to allow passing the "startup-event" flag to upstart. This is required to start friendly-recovery using upstart before any of the regular "on startup" jobs. Otherwise we'd have had to patch all the upstart jobs declaring "start on startup" or avoid using upstart entirely.
 - Add support for read-only and read/write recovery into friendly-recovery. Previous friendly-recovery would essentially start once most of the system services are already running and using read/write access to the FS.


UI Freeze Exception:
 - The recovery menu after this change is quite different. Instead of getting all the available options, the user is offered with only the subset that can run in read-only mode and an extra option to switch to read/write mode. Selecting that option then shows the usual set of options. I don't know if our documentation contains screenshot of the recovery mode, if it does, then these will need updating.

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