Hello,
2017-06-26 12:05 GMT-03:00 Istvan Szukacs:
>
> [...] I do not want
> logging, ntp and all the other crap that got sucked into it. I understand
> that service files are much better that shell scripts and this is a good
> argument but it does not justify the idiocracy that systemd became in
On Wed, 28 Jun 2017 22:31:12 -0300
Guillermo wrote:
> 2017-06-28 14:40 GMT-03:00 Steve Litt:
> >
> > On Mon, 26 Jun 2017 14:53:50 + "Laurent Bercot" wrote:
> >>
> >> The problem with the runit model is that it is pure supervision -
> >> it does not provide
2017-06-28 14:40 GMT-03:00 Steve Litt:
>
> On Mon, 26 Jun 2017 14:53:50 + "Laurent Bercot" wrote:
>>
>> The problem with the runit model is that it is pure supervision -
>> it does not provide service management. You have to run all your
>> oneshots _before_ you can start longruns.
>
> Not
Hi!
On Wed, Jun 28, 2017 at 01:40:18PM -0400, Steve Litt wrote:
> The truth of the preceding statement depends entirely on your
> priorities. If you prioritize simplicity over software orthodoxy, built
> in process ordering, and a maximally recoverable boot instance, you'll
> prefer runit. That's
Hi,
2017-06-27 16:51 GMT-03:00 Daniel GSJ:
>
> Once stage 2 is reached, the computer hangs in the same way than when
> executing *agetty* in an active console tty, and doesn't login neither.
>
> My o.s. is build with Linux-from-scratch, and is running SystemV, so it is
> a pretty simple system.
>
On Wed, 28 Jun 2017 12:44:28 -0400
Steve Litt wrote:
> 2) Install s6, but run it strictly as a process supervisor
You'd quickly run into dependency problems this way, though. There's a
reason why we have service managers such as s6-rc and anopa.
s6 is powerful on is
On Mon, 26 Jun 2017 18:17:29 +0300
Jean Louis wrote:
> I am user of s6 for reason of simplicity and to avoid trouble of
> systemd.
>
> While not being developer, maybe it could be possible to have s6 run
> systemd as a service
Euuu!
> and systemd to run s6 as a