From: "Hoël Bézier" <hoelbezier@riseup.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] sinit (suckless init) + daemontools-encore on Gentoo
Date: Thu, 14 Nov 2024 23:02:23 +0100 [thread overview]
Message-ID: <ZzZzcGbBx4VtW4ZF@sparta> (raw)
In-Reply-To: <CAJzVb5ySUzDsg_d4m36kwUoj3wd6_3JhzLx_4=gUmBQOAONfjQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1159 bytes --]
Am Di, Nov 05, 2024 am 10:44:48 -0300 schrieb Eduardo Santos:
>I searched for sinit on the gentoo-user archives and couldn't find
>anything, there's only a few Reddit threads which don't help much. Would it
>be possible to follow the steps here[1] to use sinit + daemontools-encore
>on Gentoo, or are there hard dependencies on OpenRC that make this
>impossible?
>
>This is completely for fun. I'm aware of discussions of this init vs. that
>init and I don't hate systemd/OpenRC or anything like that. Again, this is
>just for fun.
>
>I'm willing to do a lot of work myself to make this work, but if Portage or
>some other core Gentoo subsystem doesn't play well with sinit or
>daemontools-encore it'd be just a waste of time.
>
>[1] https://troubleshooters.com/linux/diy/suckless_init_on_plop.htm
Chiming in a bit late, but what you want to do would be totally feasible: I
actually run gentoo with s6-linux-init (instead of sinit) and s6 (instead of
daemontools-encore). As someone else said, the most troublesome part is writing
service scripts for every service I need since none are provided by gentoo
packages.
Have fun. :)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-11-14 22:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-06 1:44 [gentoo-user] sinit (suckless init) + daemontools-encore on Gentoo Eduardo Santos
2024-11-06 19:43 ` Jack
2024-11-06 19:50 ` Eli Schwartz
2024-11-06 21:13 ` Arve Barsnes
2024-11-14 22:02 ` Hoël Bézier [this message]
2024-11-15 1:25 ` [gentoo-user] s6 init: Was " Jack Ostroff
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZzZzcGbBx4VtW4ZF@sparta \
--to=hoelbezier@riseup.net \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox