On Wed, Jun 05, 2024 at 05:49:53PM -0400, Hendrik Boom wrote:
> 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
> >
...
...
> >
> > 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?

I gather that the various short scripts on https://smarden.org/runit/runscripts
are supposed to go into the various /etc/* directories that describe
a service to runit or daemontools. But I seem to remember that there's
more information needed to fill out one of these directories.

Or have I completely misunderstood it all?

-- hendrik

>
> (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.
> _______________________________________________
> Dng mailing list
> Dng@???
> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng