News for hackers. Stuff that matters.
Re:Debian: Transition plan to systemd by default by falcolas on Monday February 23, 2015 @09:40AM (#9094481)
> This will lead to a lot more efficient and maintainability of the Linux OS

How does consolidating functionality and control into one piece of software increase efficiency and maintainability? In my past experience, monolithic software efforts can be more efficient in the beginning, but they quickly become a maintenance nightmare as fewer and fewer people understand all of the moving parts.

You don't have to look far to see the effects of this: the Linux kernel is filled with small "I'm not sure we can remove this but I don't think it does anything" comments. You can also see it in the SaaS market as they move towards microservices, away from the monoliths of yesterday. You can see it in the giant corporate structures who take 6 months to requisition a smartphone for testing which will be obsolete in another 6 months.

The init system has the flaw of being too distributed to offer intelligent coordination between processes, but I'm not sure that following the pendulum swing to the complete opposite end of the spectrum was the best choice either.

Re:Debian: Transition plan to systemd by default by zanny on Monday February 23, 2015 @09:52AM (#9094542)
Systemd is not a big blob, it is actually fairly well structured in its source repository. Each part has its own disable flags on compilation and makes independent binaries. You should think of systemd less as a "program" and more as a software compilation for the core system.

Yes, there is a chance that components of systemd could suffer bitrot, but I'd argue its less likely that a project under the tutelage of Red Hat in the interests of its enterprise crowd will see the rot that other projects like xinetd have in recent years, where major contributors just stop, the whole project grinds to a halt, but because its not part of some broader software project nobody notices to pick up the slack (note, my example has gone through periods of rot and revival when someone notices its become a problem). If one component starts rotting the bugs will pile up on the systemd bug trackers and the broader project will notice and respond more efficiently since everything in systemd uses the same semantics and code formatting and the developers will be more comfortable changing their working directory than their repository.

Re:Debian: Transition plan to systemd by default by falcolas on Monday February 23, 2015 @10:21AM (#9094717)
> Each part has its own disable flags on compilation and makes independent binaries.

I'm not speaking of the entire systemd daemon ecosystem (which already displays coupling between logind and journald), just the systemd-as-init daemon.

> I'd argue its less likely that a project under the tutelage of Red Hat

I'd argue in return that if the Lennart Poettering bus factor suddenly went critical, systemd development would indeed hit a significant roadblock. Perhaps not insurmountable, but how many people understand the entirety of the systemd ecosystem? How many resources would RedHat be capable of devoting to this one project?

> the bugs will pile up on the systemd bug trackers

The RHEL bug tracker is currently at 250 open bugs, with 40-50 of them in the "NEW" category, with some of those dating back to 2013. The oldest open bugs date back to 2011. In my opinion, this shows a lack of bug triage, one of first outward signs of "bug pileup".

Re:Debian: Transition plan to systemd by default by vezzy-fnord on Monday February 23, 2015 @10:04AM (#9094614)
Each part has its own disable flags on compilation and makes independent binaries.

Except for generators, certain auxiliaries like rfkill, journald, udevd and others. It's rather inconsistent, as is the specific libraries that can be disabled.

Re:Debian: Transition plan to systemd by default by digi_owl on Monday February 23, 2015 @10:14AM (#9094678)
Never mind that all the "independent" binaries depends on a certain init binary sitting as pid1...
Re:Debian: Transition plan to systemd by default by bryanlarsen on Monday February 23, 2015 @09:53AM (#9094547)
What's monolithic about systemd? Sure it includes a lot of stuff, but so does Gnu coreutils and the BSD ports tree. It's not a single binary like docker.
Re:Debian: Transition plan to systemd by default by falcolas on Monday February 23, 2015 @10:28AM (#9094759)
Systemd includes no only comprehensive process management, but also socket management (to the level of listening on a socket and starting a service), device mounting, process isolation... and this is just the init daemon, not counting the remaining daemon projects which come with systemd.
Re:Debian: Transition plan to systemd by default by digi_owl on Monday February 23, 2015 @10:15AM (#9094689)
I can use a GNU cat with a busybox grep if i want to. Can i use logind with anything other than systemd-as-pid1? (btw, they really need to rename that damn init binary. But then i wonder if it is done willfully).
Re:Debian: Transition plan to systemd by default by qznc on Monday February 23, 2015 @10:35AM (#9094811)
People complained about ConsoleKit (which logind replaces) as well.

This seems to be the initial design document for logind: https://docs.google.com/document/d/1_ev4f0gwBuvs6SH_N8fN5LO4...

Re:Debian: Transition plan to systemd by default by digi_owl on Monday February 23, 2015 @10:42AM (#9094849)
Consolekit may have had its issues, but it was init agnostic.

But then seat tracking on any platform where IO devices can come and go while in operation seems like a gnarly issue to say the least.

Re:Debian: Transition plan to systemd by default by qznc on Monday February 23, 2015 @10:02AM (#9094599)
> How does consolidating functionality and control into one piece of software increase efficiency and maintainability?

Because people working on components that interact with each other are working in the same project now. They see each others commits. They see each others question on the mailing list. etc.

Let me ask the reverse question: How would this be improved by splitting systemd into independent projects?