* is there a rationale for YP using sysvinit as default init manager?
@ 2019-11-21 19:02 Robert P. J. Day
2019-11-21 20:40 ` Richard Purdie
0 siblings, 1 reply; 6+ messages in thread
From: Robert P. J. Day @ 2019-11-21 19:02 UTC (permalink / raw
To: Yocto discussion list
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 systems didn't need the flashy features of
systemd, and so on.
is there any short answer to give to that question?
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: is there a rationale for YP using sysvinit as default init manager?
2019-11-21 19:02 is there a rationale for YP using sysvinit as default init manager? Robert P. J. Day
@ 2019-11-21 20:40 ` Richard Purdie
2019-11-21 21:08 ` Paul Eggleton
0 siblings, 1 reply; 6+ messages in thread
From: Richard Purdie @ 2019-11-21 20:40 UTC (permalink / raw
To: Robert P. J. Day, Yocto discussion list
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 systems didn't need the flashy features of
> systemd, and so on.
>
> is there any short answer to give to that question?
The project existed before systemd and we haven't changed the default.
We can change the default, it just means someone going through and
fixing the build failures it generates and rewriting all the test
metadata to invert poky and poky-altcfg. Personally I've got other
things I'd prefer to do...
Cheers,
Richard
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: is there a rationale for YP using sysvinit as default init manager?
2019-11-21 20:40 ` Richard Purdie
@ 2019-11-21 21:08 ` Paul Eggleton
2019-11-21 21:14 ` Richard Purdie
0 siblings, 1 reply; 6+ messages in thread
From: Paul Eggleton @ 2019-11-21 21:08 UTC (permalink / raw
To: Robert P. J. Day, Kai Kang; +Cc: yocto
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 suggested it was for simplicity and reliability,
> > and that a lot of embedded systems didn't need the flashy features of
> > systemd, and so on.
> >
> > is there any short answer to give to that question?
>
> The project existed before systemd and we haven't changed the default.
>
> We can change the default, it just means someone going through and
> fixing the build failures it generates and rewriting all the test
> metadata to invert poky and poky-altcfg. Personally I've got other
> things I'd prefer to do...
Kai was working on changing this in the last cycle but AFAICT not all issues
were able to be resolved in time. Kai, do you have a status update?
Thanks
Paul
--
Paul Eggleton
Intel System Software Products
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: is there a rationale for YP using sysvinit as default init manager?
2019-11-21 21:08 ` Paul Eggleton
@ 2019-11-21 21:14 ` Richard Purdie
2019-11-21 21:35 ` Alexander Kanavin
0 siblings, 1 reply; 6+ messages in thread
From: Richard Purdie @ 2019-11-21 21:14 UTC (permalink / raw
To: Paul Eggleton, Robert P. J. Day, Kai Kang; +Cc: yocto
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 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 systems didn't need the flashy
> > > features of
> > > systemd, and so on.
> > >
> > > is there any short answer to give to that question?
> >
> > The project existed before systemd and we haven't changed the
> > default.
> >
> > We can change the default, it just means someone going through and
> > fixing the build failures it generates and rewriting all the test
> > metadata to invert poky and poky-altcfg. Personally I've got other
> > things I'd prefer to do...
>
> Kai was working on changing this in the last cycle but AFAICT not all
> issues were able to be resolved in time. Kai, do you have a status
> update?
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 testing of
systemd on a near enough equal footing to sysvinit which was the
concern people had raised. There are problems in oe-selftest and some
other corner cases but nothing people seem to be running into day-to-
day.
There has been representation at OE meetings, in surveys and from YP
members for us not to switch the default FWIW.
Cheers,
Richard
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: is there a rationale for YP using sysvinit as default init manager?
2019-11-21 21:14 ` Richard Purdie
@ 2019-11-21 21:35 ` Alexander Kanavin
2019-11-22 7:23 ` [yocto] " Josef Holzmayr
0 siblings, 1 reply; 6+ messages in thread
From: Alexander Kanavin @ 2019-11-21 21:35 UTC (permalink / raw
To: Richard Purdie; +Cc: Paul Eggleton, Yocto discussion list
[-- Attachment #1: Type: text/plain, Size: 828 bytes --]
On Thu, 21 Nov 2019 at 22:18, Richard Purdie <
richard.purdie@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 testing of
> systemd on a near enough equal footing to sysvinit which was the
> concern people had raised. There are problems in oe-selftest and some
> other corner cases but nothing people seem to be running into day-to-
> day.
>
It is also quite amazing that the project, by design, has entirely
sidestepped the divisive init system wars that have been gripping the
mainstream linux distros for years (and still are). I'd say it hardly
matters what the default is, if the other options are well supported.
Alex
[-- Attachment #2: Type: text/html, Size: 1165 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [yocto] is there a rationale for YP using sysvinit as default init manager?
2019-11-21 21:35 ` Alexander Kanavin
@ 2019-11-22 7:23 ` Josef Holzmayr
0 siblings, 0 replies; 6+ messages in thread
From: Josef Holzmayr @ 2019-11-22 7:23 UTC (permalink / raw
To: Alexander Kanavin; +Cc: Richard Purdie, Paul Eggleton, Yocto discussion list
On Thu, Nov 21, 2019 at 10:35:39PM +0100, Alexander Kanavin wrote:
> On Thu, 21 Nov 2019 at 22:18, Richard Purdie <
> richard.purdie@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 testing of
> > systemd on a near enough equal footing to sysvinit which was the
> > concern people had raised. There are problems in oe-selftest and some
> > other corner cases but nothing people seem to be running into day-to-
> > day.
> >
>
> It is also quite amazing that the project, by design, has entirely
> sidestepped the divisive init system wars that have been gripping the
> mainstream linux distros for years (and still are). I'd say it hardly
> matters what the default is, if the other options are well supported.
>
> Alex
Thats my take as well. By sysv being the default andsystemd being
massively used we almost automatically end up with good testing of both.
Greetz
--
———————————————
Josef Holzmayr
Software Developer Embedded Systems
Tel: +49 8444 9204-48
Fax: +49 8444 9204-50
R-S-I Elektrotechnik GmbH & Co. KG
Woelkestrasse 11
D-85301 Schweitenkirchen
www.rsi-elektrotechnik.de
———————————————
Amtsgericht Ingolstadt – GmbH: HRB 191328 – KG: HRA 170393
Geschäftsführer: Dr.-Ing. Michael Sorg, Dipl.-Ing. Franz Sorg
Ust-IdNr: DE 128592548
_____________________________________________________________
Amtsgericht Ingolstadt - GmbH: HRB 191328 - KG: HRA 170363
Geschäftsführer: Dr.-Ing. Michael Sorg, Dipl.-Ing. Franz Sorg
USt-IdNr.: DE 128592548
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2019-11-22 7:24 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2019-11-21 19:02 is there a rationale for YP using sysvinit as default init manager? Robert P. J. Day
2019-11-21 20:40 ` Richard Purdie
2019-11-21 21:08 ` Paul Eggleton
2019-11-21 21:14 ` Richard Purdie
2019-11-21 21:35 ` Alexander Kanavin
2019-11-22 7:23 ` [yocto] " Josef Holzmayr
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.