On Wed, 2019-09-11 at 19:20 +0200, Ansgar wrote:
> Control: clone -1 -2 -3
> Control: reassign -2 initramfs-tools
> Control: reassign -3 dracut
> Control: retitle -2 initramfs-tools: fallback to /lib/systemd/systemd if 
> init=/bin/systemd
> Control: retitle -3 dracut: fallback to /lib/systemd/systemd if 
> init=/bin/systemd
> Control: block -1 by -2
> Control: block -1 by -3
> Dear initramfs maintainers,
> would it be possible to add a fallback to try /lib/systemd/systemd if
> the user provided init=/bin/systemd and the file no longer exists?
> I would like systemd to stop shipping the /bin/systemd symlink as this
> should not be run by users, however it was suggested to use
> init=/bin/systemd for testing purposes in the past (see below).  So just
> removing the symlink might make some systems unbootable.

I don't think it's appropriate for the initramfs to do this sort of
magic.  Even if they did, this wouldn't cover systems using a custom
kernel that doesn't need an initramfs.

I think that a better way to handle this would be for systemd itself to
warn on upgrade if /proc/cmdline contains init=/bin/systemd.


Ben Hutchings
Unix is many things to many people,
but it's never been everything to anybody.

Attachment: signature.asc
Description: This is a digitally signed message part

Reply via email to