From: Guillermo <gdiazhartusch@gmail.com>
To: Supervision <supervision@list.skarnet.org>
Subject: Re: interesting claims
Date: Sun, 19 May 2019 17:35:00 -0300 [thread overview]
Message-ID: <CADQ2Nw9YjpoSsz6hh7JphvzCM0HJkztfokAcps=U26S1U-KTSg@mail.gmail.com> (raw)
In-Reply-To: <d1a7fe4d-19cb-db6d-b322-8e9e00af06a4@obarun.org>
El dom., 19 may. 2019 a las 8:24, fungal-net escribió:
>
> [...]
> 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.
As far as I can tell, at the moment it has a sysvinit + OpenRC setup,
plus an s6 supervision tree anchored to process #1. Unlike other
distributions, the getty processes are part of the supervision tree,
and placed there by an Adélie-specific OpenRC service in the sysinit
runlevel.
> One of the reasons I am trying to learn more about init in general and
> porting s6 to a different system is to use either Adélie or Void-musl
> and have pure s6 on them.
I believe Adélie is heading towards supporting that.
> 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.
Really? As far as I can tell, Void's s6-rc is the unmodified upstream
package, and Void's 66 is the unmodified package from Obarun's
repository.
> Void uses arch-like /bin /sbin --> /usr/bin, Adélie has more traditional
> 4 separate directories.
Yeah, that's both /usr-merge and bin-sbin merge. A whole discussion in itself.
G.
next prev parent reply other threads:[~2019-05-19 20:35 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-29 19:19 Jeff
2019-04-30 2:49 ` Guillermo
2019-04-30 8:22 ` Laurent Bercot
2019-05-03 0:53 ` what init systems do you use ? Jeff
2019-05-11 18:45 ` Guillermo
2019-05-13 19:13 ` multiplexd
2019-05-13 20:36 ` Laurent Bercot
2019-05-13 21:09 ` Steve Litt
2019-05-14 2:34 ` Guillermo
2019-05-13 21:16 ` Joshua Ismael Haase Hernández
2019-05-14 5:50 ` Colin Booth
2019-05-14 7:15 ` eric vidal
2019-04-30 8:47 ` interesting claims Jonathan de Boyne Pollard
2019-05-01 7:26 ` Steve Litt
2019-05-01 7:33 ` Steve Litt
2019-05-01 18:13 ` Laurent Bercot
2019-05-15 17:22 ` Steve Litt
2019-05-15 23:22 ` Oliver Schad
2019-05-16 1:07 ` Steve Litt
2019-05-16 5:36 ` fungal-net
2019-05-16 8:32 ` Laurent Bercot
2019-05-16 17:10 ` Jeff
2019-05-17 0:23 ` Dewayne Geraghty
2019-05-17 11:21 ` fungal-net
2019-05-17 22:57 ` Guillermo
2019-05-18 0:52 ` Jeff
2019-05-18 16:26 ` fungal-net
2019-05-18 20:04 ` Guillermo
2019-05-19 11:24 ` fungal-net
2019-05-19 12:57 ` killall test run Jeff
2019-05-19 17:29 ` Colin Booth
2019-05-19 20:39 ` Guillermo
2019-05-19 23:06 ` Laurent Bercot
2019-05-19 20:35 ` Guillermo [this message]
2019-05-03 1:37 ` how to handle system shutdown ? Jeff
2019-05-03 19:25 ` Laurent Bercot
2019-05-05 0:52 ` is it required to call kill() from process #1 ? Jeff
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='CADQ2Nw9YjpoSsz6hh7JphvzCM0HJkztfokAcps=U26S1U-KTSg@mail.gmail.com' \
--to=gdiazhartusch@gmail.com \
--cc=supervision@list.skarnet.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;
as well as URLs for NNTP newsgroup(s).