Bug#757298: Please add fallback boot entry for sysvinit when systemd is the active init
Michael Biebl
biebl at debian.org
Thu Aug 7 01:53:35 BST 2014
Package: grub-common
Version: 2.02~beta2-11
Severity: normal
Tags: patch
User: pkg-systemd-maintainers at lists.alioth.debian.org
Usertags: integration
Hi,
in [1] we laid out the plan how we want to manage the transition to
systemd as the default init on Linux for Jessie.
One aspect of that transition plan, is to make sysvinit a transitional
package (step b/) which provides a fallback /lib/sysvinit/init binary.
So even if systemd is the default init and the /sbin/init binary is
provided by systemd-sysv one can use the init=/lib/sysvinit/init boot
parameter to boot using the old sysvinit system.
This is intended as a fallback mechanism in case the system fails to
boot with systemd so users have a simpler method to recover the system
and examine the failure.
To make this even more straightforward, we suggest that grub provides a
menu entry for that sysvinit fallback.
Attached is patch achieving that.
I think it would be reasonable to drop this feature again in jessie+1 or
jessie+2.
Once this patch has been applied to grub, I sysvinit would have to be
updated to call update-grub in postinst on install|upgrade and postrm
on remove to ensure the menu entry is up-to-date.
Do you have any suggestions regarding the the usage of update-grub?
Your feedback would be most welcome.
Michael
[1] https://lists.debian.org/debian-devel/2014/07/msg00611.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: grub2.diff
Type: text/x-diff
Size: 1056 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-systemd-maintainers/attachments/20140807/925de743/attachment-0001.diff>
More information about the Pkg-systemd-maintainers
mailing list