On Mon, Jun 03, 2024 at 10:15:54PM -0400, Steve Litt wrote:
> altoid via Dng said on Sat, 01 Jun 2024 18:16:37 -0300
>
> >There is and will always be a lot of moolah behind the use of systemd
> >in Linux and Debian has been the Trojan Horse used to achieve the
> >first part of that goal.
> >
> >Now, the system has been infected and the infection is growing fast.
> >
> >With the aid of Poettering and his crew of MS/IBM/RH misfits, the
> >pustch against the Linux ecosystem continues while within Linux the
> >few that care are talking about/discussing multiple init softwares
> >instead of investing their time and efforts to make dead sure that at
> >least 'one' works without needing systemd.
> >
> >No matter *which* one. Just one that works and can use all the
> >available packages.
> >
> >Sooner than later, not *one* package in the Debian repositories will
> >have an initscript and as a result absolutely *everything* Devuan
> >will be dead in the water.
> >
> >I'm sure that everyone will then be very happy to have the *choice*
> >of only one Linux-like (if you may call it that) OS to choose from.
> >
> >And that day, Microsoft's wet dream will have become a reality.
> >
> >Unbelievable.
> >But close but with every day that goes by closer to being the truth.
>
> Altoid, you can fix this, by yourself, with 80 hours of work. If you
> do, even though I'm busier that a 1 legged man in a butt kicking
> contest, I'll help you with design, documentation and publicity.
>
> All you need to do is provide a tarball of runit, stage 2, including
> run directories most of the daemons you need, in a single directory
> tree. A lot of this is simply copying the material from
> https://smarden.org/runit/runscripts . You can also grab and modify
> slightly the Void Linux' run directories and run scripts.

Looking at https://smarden.org/runit/runscripts and at
https://github.com/void-linux/runit
I don't have much of an idea what you're asking to be done.
I guess I don't yet have enough understanding of runit's source code.
Where should I find more understanding?

(No, I'm not committing to do this work. It looks like a worthwhile project,
but I refuse to even consider comitting until I understand what needs
to be done.)
>
> Why a tarball of a singular directory tree? Because it's an end run
> around the packaging system, meaning a systemd sycophant can't package
> your solution out of their distro. By the way, the top level of the
> tree would look something like the following:
>

> altoid_runit
>    src
>    sv_all
>    sv_active

>
> sv_all would be every single run directory that can be discovered by
> any means, whether or not its daemon is installed on the computer. This
> separates the run script from the upstream author so he doesn't need to
> create the run script.
>
> sv_active would be a bunch of symlinks to directories in sv_all,
> because each of these symlinks enables runit to supervise the daemon
> for the symlink.
>
> The user could put this tree anywhere. It could be owned by root, or
> perhaps a properly crafted user/group named runit. A few symlinks can
> be used to adjust it to the distro or the user's principles and
> prejudices.
>
> Why a single tree? Because you can then install simply by laying down
> the tree, setting a few environment variables, and compiling the (very
> simple and easy to compile) runit executables, for which there are
> already make files at runit-2.1.2.tar.gz , or if you want to include
> upgrades since 2014, perhaps get it from the Void Linux project, at
> github.com/void-linux/runit , because Void are the official maintainers
> now. Remember, the reason for packages is the "we include 40
> dependencies you don't need but must have for our package" take it or
> leave it. Other than the C standard library, I don't think runit
> includes anything not part of the runit software's source code.