is there a rationale for YP using sysvinit as default init manager?
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
Signature · 7 lines
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================Quoted 7 lines · Robert P. J. Day
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
Quoted 7 lines · NZDT Richard Purdie
Quoted 6 lines · Robert P. J. Day
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.
Quoted 8 lines
Quoted 1 line
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
Signature · 2 lines
Paul Eggleton Intel System Software Products
Quoted 17 lines · Paul Eggleton
Quoted 16 lines · NZDT Richard Purdie
Quoted 11 lines · Robert P. J. Day
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.
Quoted 8 lines
Quoted 4 lines
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
Quoted 8 lines · Richard Purdie
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
Quoted 12 lines · Alexander Kanavin
Quoted 8 lines · Richard Purdie
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.
Quoted 6 lines
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
Signature · 20 lines
——————————————— 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