Re: [yocto] is there a rationale for YP using sysvinit as default init manager?

2019-11-21 Thread Alexander Kanavin
On Thu, 21 Nov 2019 at 22:18, Richard Purdie < richard.pur...@linuxfoundation.org> wrote: > We got so far and after looking at the position we ended up I decided > it was easier to switch poky-altcfg rather than change poky and/or OE > defaults. I resolved that bug as "complete" as we now had

Re: [yocto] is there a rationale for YP using sysvinit as default init manager?

2019-11-21 Thread Richard Purdie
On Fri, 2019-11-22 at 10:08 +1300, Paul Eggleton wrote: > On Friday, 22 November 2019 9:40:35 AM NZDT Richard Purdie wrote: > > On Thu, 2019-11-21 at 14:02 -0500, Robert P. J. Day wrote: > > > don't get me wrong, i have no problem with that, but a > > > colleague > > > asked me what the reason

Re: [yocto] is there a rationale for YP using sysvinit as default init manager?

2019-11-21 Thread Paul Eggleton
On Friday, 22 November 2019 9:40:35 AM NZDT Richard Purdie wrote: > On Thu, 2019-11-21 at 14:02 -0500, Robert P. J. Day wrote: > > don't get me wrong, i have no problem with that, but a colleague > > asked me what the reason was for using sysvinit as the *default*. i > > hemmed and hawed and

Re: [yocto] is there a rationale for YP using sysvinit as default init manager?

2019-11-21 Thread Richard Purdie
On Thu, 2019-11-21 at 14:02 -0500, Robert P. J. Day wrote: > don't get me wrong, i have no problem with that, but a colleague > asked me what the reason was for using sysvinit as the *default*. i > hemmed and hawed and suggested it was for simplicity and reliability, > and that a lot of embedded