Indeed, the upstart job should be a task, updated in my copy. Sadly the upstart job doesn't work at the moment, I tried a few variations without much luck and e-mailed James Hunt to see if "start on starting mountall" is supposed to work at all in this particular case.
It seems like I'd need to start friendly-recovery from the pre-start script if I want to make sure mountall doesn't start or I'd need to do a "stop $JOB" to prevent it from starting. Neither of these work, both successfully block mountall but I end up with an empty console and no recovery menu. That FIXME indeed doesn't make much sense anymore, I added it before I switched to "start on starting". I think for now it's safe to just keep the current duplicate code (that had to be changed quite a bit anyway) and I'll change the FIXME for another comment saying why we're doing it this way. I'll have these changed in my local copy and wait for feedback from James on getting the upstart job working. Worst case, I'll revert to using the startup-event boot parameter which needs a change in initramfs-tools but works perfectly. -- 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: [UIFe] [FFe] recovery mode mounts filesystems read-write rather than read-only To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/575469/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
