Le 04/01/2022 à 03:08, Steve Litt a écrit :
k...@aspodata.se said on Mon, 3 Jan 2022 18:45:28 +0100 (CET)
Would there be any interests having a busybox_init package which
I could possible maintain (with a little help) ?
My opinion is that the more init systems the merrier, except for
systemd.
If busybox init does not require daemons to self-background, I'd be
even more enthusiastic.
SteveT
Busybox init is merely a simplified replacement for sysvinit. As
sysvinit, it can be used to invoke either the famous scripts invoquing
servers which background themselves or any supervisor or launcher of
your choice.
The striking feature of Busybox, in the context of a /usr merge, is
that it has no runtime dependency if you build it as a statically linked
executable, which is probably the most popular way to build it. I.e. it
does not need a shared library to run, therefore does not depend on
anything in /usr. And it provides anything you would find in /bin and
/sbin and all the base system utilities you can find in /usr/bin and
/usr/sbin. When you configure it, you just specify the applictions you want.
-- Didier
_______________________________________________
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
