DebianThis forum is for the discussion of Debian Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Regardless the technical questions, Systemd is linux-only so they will have to come up with some sort of compatibility workarounds, Upstart requires you to sign the CLA to contribute upstream and i'm not sure how the Debian policy rules apply to this. OpenRC doesn't seem to be a serious advancement from sysVinit.
If Debian chooses Upstart it might be serious setback for systemd.
No.
It's from the majority (not everyone) of all DD/DM's and really about Debian and Debian only ...
Quote:
It is more and more obvious that modern software needs an event-based
init system.
Pros:
- more features
- stable support for advanced boot/SAN environments
- being more similar to one of the other relevant distributions (RHEL or
Ubuntu)
- things like gnome become easier to package
Cons:
- some work to do (how much depends on the choice and on the details.
but keeping sysvinit on life support is not free either)
Since the init system strongly shapes many other packages, there has to
be only one and no other supported options.
Options:
*sysvinit (status quo)
*systemd
*upstart
*openrc (not available in sid - ITP: 684396)
*One system on Linux, something else on non-linux
*multiple: commit to supporting two or more specific initsystems, such that choosing a default is less important, and at least one of them is available to every arch
Traditional SysV is lacking features for some user-cases/environments in Debian (blocking release goals for Jessie).
Supporting them all the same would be a mess.
OpenRC isn't even available in Sid.
So ... it's mostly about "upstart vs systemd" (+ a solution for kFreeBSD an Hurd if possible).
And I can understand why there has been push-back. I always thought Linux was about choice - I'll start what I want when I want.
Not accept an image pushed down my throat by the devs.
And I can understand why there has been push-back.
What push-back are you referring to? I've not seen any discussion of this new idea for an init system. I'd really like to see some though: do you have any links?
I was extrapolating from the (translation of) the article
Ok. I don't find that last paragraph to be particularly surprising, and I don't really think of it as push-back against this new idea in particular. From what I've seen the upstart backers and systemd backers have already made up their minds and are unlikely to be swayed easily.
Which actually sets out the proposed possibilities quite well and I found quite interesting.
It really is not about "starting things when you want" as init already starts thing automatically when you boot. Yes you can change the order if you want but I don't see anything stopping you from doing that with the top three choices.
Upstart I doubt will be used. It is not that great anyway and the copyright policy of Canonical is offensive to too many people.
Systemd is used quite well by some distros already. I know it works fine in Mageia 3.
The only real objection to changing is that it is change or so it seems to me. There is some sense to that argument but there was the same sense in arguing for sticking with many systems that have now disappeared from use.
The objection of the systemd devs to porting it to other kernels than the Linux kernel seems like the only logical objection but that could be handled by a fork or by their becoming a bit more flexible in their thinking.
Be interesting to see what Debian does do with this. I suspect more integration of systemd, for which there is considerable support already in Debian, as sticking with init for Jessie as with Wheezy. Then a shift to systemd for Debian 9.
I think that is just more in line with the traditional way of change in Debian.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.