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