Re: [DNG] Lead BusyBox developer on sysvinit

2016-02-19 Thread Rainer Weikusat
- I'm using a wireless Logitech USB keyboard which acts just like an unreliable datagram service, ie, it loses, reorders or duplicates keystrokes whenever it feels like that (wired version of the same model is no better) - Didier Kryn writes: > Le 18/02/2016 18:05, Steve

Re: [DNG] Lead BusyBox developer on sysvinit

2016-02-19 Thread Rainer Weikusat
Didier Kryn writes: > Le 18/02/2016 18:05, Steve Litt a écrit : >> On Thu, 18 Feb 2016 16:15:55 +0100 >> Didier Kryn wrote: >> >>> > Hence the argument already exposed by several persons on this >>> >list, in particular Laurent: let's pid1 do*only* what no

Re: [DNG] Lead BusyBox developer on sysvinit

2016-02-19 Thread Rainer Weikusat
Didier Kryn writes: > Le 19/02/2016 00:19, Rainer Weikusat a écrit : >> Didier Kryn writes: >> >> [...] >> >>That's a theoretical argument I agree with: I think the server/ service >>management code shouldn't be part of init especially since it's

Re: [DNG] Lead BusyBox developer on sysvinit

2016-02-19 Thread Didier Kryn
Le 18/02/2016 18:05, Steve Litt a écrit : On Thu, 18 Feb 2016 16:15:55 +0100 Didier Kryn wrote: > Hence the argument already exposed by several persons on this >list, in particular Laurent: let's pid1 do*only* what no other >program can do.

Re: [DNG] Lead BusyBox developer on sysvinit

2016-02-19 Thread Didier Kryn
Le 19/02/2016 00:19, Rainer Weikusat a écrit : Didier Kryn writes: [...] >>That's a theoretical argument I agree with: I think the server/ service >>management code shouldn't be part of init especially since it's >>virtually unused but that's really a tiny addition to the

Re: [DNG] Lead BusyBox developer on sysvinit

2016-02-18 Thread Rainer Weikusat
Steve Litt writes: [...] > My opinion is that although this is indeed a bad thing, I'm > willing to risk it to get the breathtaking simplicity of Rich > Felker's vision in http://ewontfix.com/14/. Process #1 doesn't receive signals unless it installed a handler for

Re: [DNG] Lead BusyBox developer on sysvinit

2016-02-18 Thread Rainer Weikusat
Didier Kryn writes: > Le 18/02/2016 17:15, Rainer Weikusat a écrit : >> I suspect that many people who are >> (unspecifically) 'offended' by that suffer from a bad case of "But >> that's not how I would have done it!" disease as it's written in a more >> traditional UNIX(*) style

Re: [DNG] Lead BusyBox developer on sysvinit

2016-02-18 Thread Steve Litt
On Thu, 18 Feb 2016 16:15:55 +0100 Didier Kryn wrote: > Hence the argument already exposed by several persons on this > list, in particular Laurent: let's pid1 do *only* what no other > program can do. NOTE: My response is

Re: [DNG] Lead BusyBox developer on sysvinit

2016-02-18 Thread Didier Kryn
Le 18/02/2016 17:15, Rainer Weikusat a écrit : I suspect that many people who are (unspecifically) 'offended' by that suffer from a bad case of "But that's not how I would have done it!" disease as it's written in a more traditional UNIX(*) style which has gone thoroughly out of fashion more

Re: [DNG] Lead BusyBox developer on sysvinit

2016-02-18 Thread Rainer Weikusat
Didier Kryn writes: > Le 18/02/2016 12:37, Rainer Weikusat a écrit : >> I mean that "Do you trust this code! It had at least one bug!" is a >> silly statement. > I didn't read the same thing as you. > > I read more trust is needed in pid1 than in any other program. I > also

Re: [DNG] Lead BusyBox developer on sysvinit

2016-02-18 Thread Didier Kryn
Le 18/02/2016 12:37, Rainer Weikusat a écrit : I mean that "Do you trust this code! It had at least one bug!" is a silly statement. I didn't read the same thing as you. I read more trust is needed in pid1 than in any other program. I also read one cannot trust a program just because

Re: [DNG] Lead BusyBox developer on sysvinit

2016-02-18 Thread Rainer Weikusat
Didier Kryn writes: > Le 17/02/2016 22:56, Rainer Weikusat a écrit : >> Mitt Green writes: >>> >In case you haven't read this, >>> >Denys Vlasenko tells about >>> >his experiences with sysvinit. >>> >There he refers to daemontools >>> >and runit as superior

Re: [DNG] Lead BusyBox developer on sysvinit

2016-02-18 Thread Didier Kryn
Le 17/02/2016 22:56, Rainer Weikusat a écrit : Mitt Green writes: >In case you haven't read this, >Denys Vlasenko tells about >his experiences with sysvinit. >There he refers to daemontools >and runit as superior to the traditional >init. >

Re: [DNG] Lead BusyBox developer on sysvinit

2016-02-17 Thread Steve Litt
On Wed, 17 Feb 2016 21:56:49 + Rainer Weikusat wrote: > Mitt Green writes: > > In case you haven't read this, > > Denys Vlasenko tells about > > his experiences with sysvinit. > > There he refers to daemontools > > and runit as superior

Re: [DNG] Lead BusyBox developer on sysvinit

2016-02-17 Thread Rainer Weikusat
Mitt Green writes: > In case you haven't read this, > Denys Vlasenko tells about > his experiences with sysvinit. > There he refers to daemontools > and runit as superior to the traditional > init. > > https://busybox.net/~vda/init_vs_runsv.html Wrt "Do you trust this code"

[DNG] Lead BusyBox developer on sysvinit

2016-02-17 Thread Mitt Green
Hi, In case you haven't read this, Denys Vlasenko tells about his experiences with sysvinit. There he refers to daemontools and runit as superior to the traditional init. https://busybox.net/~vda/init_vs_runsv.html Mitt ___ Dng mailing list