Ralph Ronnquist via Dng said on Thu, 19 Jun 2025 10:19:21 +1000

>What is supposed to be in /lib/sysvinit/init ? That's not a realised
>pathname on my setup, and that is not where the init binary of
>sysvinit-core is installed. Perhaps there was some attempt at som
>point to have sysvinit's init installed there?
>
>From memory, the kernel looks for "/init", "/sbin/init" or "/bin/init"
>(in order) to tbe the initial process, and the pathname may be a
>symbolic link to an actual file which may be a binary or a "#!"
>script.

I think you're right, and that's great because you can change the init
system for your next boot by copying PID1 from sysvinit or runit or s6
or Epoch or (gulp) OpenRC to /sbin and making it executable. I've done
this, and it worked. This also gives you a great way to bust back in
with a rescue CD or Thumb if your current /init becomes hopelessly
unbootable (for instance, if it's systemd).

The best thing about this technique is I don't need to mess with that
awful grub2.

SteveT

Steve Litt

http://444domains.com