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

[Steve Langasek]

Do we really need to change the ui, here?  What if we used the existing
friendly-recovery options to decide whether or not to tell mountall to
mount read-write?  I guess the choice of recovery options that require
read-write disk is rather clear.

I also am not nearly as worried about the UI change as I would be about
the new code being written for mountall (which would violate FFe).  We
would need a UI freeze exception, true, but UI Freeze is primarily about
*coordinating* changes, not about forbidding them entirely - and this is
a significant enough bug in the recovery mode that I think all users are
better off with a possibly-untranslated facility than with not having
the facility at all.  Whereas the mountall changes are risky and could
make recovery mode less stable / usable for everyone.

-- 
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 “friendly-recovery” source package in Oneiric:
  Confirmed

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