killall test run

[Jeff <sysinit@yandex.com>]

19.05.2019, 13:24, "fungal-net" <fungalnet@obarun.org>:
> I am glad some of you can tell more than I can about this, and since you
> did I tried my weirdest of setups. This is Adélie adelielinux.org
> installation on HD. Although it is confusing to me how they set this up
> still, after months of following its development (beta3), there is
> sysvinit on the first steps of booting then OpenRC takes over, and then
> s6-supervisor handles everything running. It is like a fruit punch in
> my eyes. For those that don't know this is built on musl.

they use SysV init + OpenRC (with some scripts from Alpine)
OpenRC is known to work with s6-svscan (this is done via the
/libexec/rc/sh/s6.sh shell script). although it is better to start
s6-svscan from /etc/inittab (directly or - as i prefer - via a starter
shell/execline script that ensures at least the scandir exists)
since SysV init can respawn processes anyway (supervised
supervisor ;-).

by default OpenRC (better: s6.sh) uses /run/openrc/s6-scan as the
service scandir and /var/svc.d as service template dir, this can
be changed easily of course since only shell scripts are involved here.
when starting an s6 service it copies the service template dir into
the scandir /run/openrc/s6-scan. for this to work properly an already
running instance of s6-svscan (that runs on said scandir) is required.
OpenRC achieves this by adding "s6-svscan" to the "need" call in
the depend function of the corresponding service script.

when starting s6-svscan from inittab OpenRC does not have to
start it and there is no need to start the s6-svscan nor to add it to
other services' dependencies. although i do not know the order
in which sysvinit processes the inittab entries for a given (SysV)
"runlevel". do "wait" entries precede "respawn" entries, followed
by the "once" entries ? dunno, this needs a bit of hackery to make
it work but this ordering/dependency problem is definitely solvable.

> # kill -9 -1 on tty1 brought me back to tty1 login screen with 5 more
> ttys active. So everything is respawned almost instantly to a system
> just like it had just booted. Doing the same from terminal on X had the
> same exact outcome.

as expected. :D

> Both s6/s6-rc and 66 pkgs are available through void's repositories but
> s6-rc has been modified and I haven't been able to get it to work.

you can find out easily about your init via
$ ps -Fjlp 1
also have a look in the /proc/1 dir when procfs is mounted on /proc,
the target of the exe symlink is of interest here.

to see how all this is organised check with
$ ps -FHjle fww
BEFORE kill -1 -9 and again after sending the kill blast.

> Void uses arch-like /bin /sbin --> /usr/bin,

yes, i noticed this too. this is not "arch" like but was invented by fedora/
red hat instead. being the fedora testbed the lame arch distro had
to follow suit immediately as is typical for them.

> Adélie has more traditional 4 separate directories.

this is what one would expect.