Ok, so I have the initial implementation of the fix.
The current chosen solution is:
- Move friendly-recovery to /lib/recovery-mode
- Make it ship its own upstart job starting on "recovery-mode"
- Update initramfs-tools to support a new boot parameter "startup-event"
that's passed to init
- U
** Changed in: friendly-recovery (Ubuntu)
Milestone: ubuntu-11.10-beta-1 => ubuntu-11.10-beta-2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/575469
Title:
recovery mode mounts filesystems read-
Sorry for the mess above, I just remembered we already had bug 234409
for the /usr part of this bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/575469
Title:
recovery mode mounts filesystems read
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, frien
Option 2 would also get us rid of bug 234409 in the process.
I still like the idea of having read-only be an option of mountall as
it'd be pretty handy to have in other cases but I guess option 2 is the
most likely to be implemented for Oneiric. It's still a pretty
significant amount of changes th
I just had a quick look at mountall and can't find any easy way to mount
everything read only. So bypassing mountall at this point means having only the
root filesystem mounted in read-only mode, which should work in most cases when
people stick to default partitioning.
It'll lead to a non worki
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
Can you not tell mountall to force ro instead of rw? It's just that
ro->rw remounts are easy and safe, while rw->ro remounts are not (you
have no guarantee that the filesystem is actually ro in this state). To
me it would have seemed like an obvious thing to mount the filesystems
ro and remount t
Ok, so looking at the current code, the problem is that friendly-
recovery is started after mountall mounted / as read-write, actually
everything that's in my fstab is mounted when friendly-reocvery starts.
Most of the options also require read/write access to the filesystem and
indeed need pretty
** Changed in: friendly-recovery (Ubuntu Oneiric)
Assignee: Surbhi Palande (csurbhi) => Stéphane Graber (stgraber)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/575469
Title:
recovery mode moun
A workaround to boot with the root mounted read-only is to edit the grub
command line so it includes "init=/bin/bash". Obviously non-ideal, but
it lets me run zerofree at least.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
** Also affects: friendly-recovery (Ubuntu Oneiric)
Importance: Undecided
Assignee: Surbhi Palande (csurbhi)
Status: Confirmed
** Changed in: friendly-recovery (Ubuntu Oneiric)
Importance: Undecided => Medium
** Changed in: friendly-recovery (Ubuntu Oneiric)
Milestone: None
** Changed in: friendly-recovery (Ubuntu)
Status: New => Confirmed
** Changed in: friendly-recovery (Ubuntu)
Assignee: (unassigned) => Surbhi Palande (csurbhi)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
They are mounted RW because of recovery-mode options like dpkg "Repair
broken packages" (actually an upgrade as per bug #45). There is an
fsck option that is invisible on Ubuntu 10.04 (Lucid Lynx) due to bug
#566200. It creates a flag file, /forcefsck, that is checked for by the
mountall.conf
14 matches
Mail list logo
