Rainer Weikusat via Dng said on Thu, 19 Jun 2025 09:57:29 +0100

>Steve Litt <slitt@???> writes:
>> 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.
>
>JFTR: It's also possible to pass init=/some/program as parameter on the
>kernel command-line to specify which program the kernel should start as
>init. In particular, init=/bin/sh or init=/bin/bash can be used to get
>a usable shell without running anything else.

That's possible, I've done it, but I really don't like fooling around
with grub2.

SteveT

Steve Litt

http://444domains.com