2 ms·
> 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 dis
by falcolas 12y ago
> 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".