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

[Stéphane Graber]

Hmm, thinking a bit more about it, I think we'll still need a change to
update-grub, replacing "single" by "rescue" so we can then have the
friendly-recovery look for "rescue" on the command line.

"single" is already caught by rc-sysvinit.conf and triggers a root
shell, that'd make the resume option of friendly-recovery start a root
shell rather than actually resuming the standard boot sequence. I don't
think that's what we want.

So I think it'd be reasonable to: 
 - Replace "single" by "rescue" in update-grub
 - Have friendly-recovery changed to "start on starting mountall" and run only if rescue is found in cmdline

This way we can still drop the initramfs-tools change and keep a working
single user mode (if a user explicitly boot appending single to the
command line).

We'd then need Breaks added to:
 - upstart (breaks old friendly-recovery that needed rcS.conf to start)
 - grub2 (breaks old friendly-recovery that needed single to start)

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