SoylentNews is people
SoylentNews
Phoronix reports the systemd developers are having their first conference. Here is a direct link to the YouTube video channel.
Whether you love systemd or hate it, it looks like it's not going away. If you dislike it maybe one of these videos might change your mind.
This discussion has been archived.
No new comments can be posted.
'systemd' Developers Have First Conference
|
Log In/Create an Account
| Top
| 105 comments
| Search Discussion
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
I consider the day misspent that I am not either charged with a crime,
or arrested for one.
-- "Ratsy" Tourbillon
(Score: 3, Interesting) by Alias on Wednesday November 11 2015, @02:41AM
I have, in the past, made the argument that systemd doesn't do anything that couldn't be done before. In fact, I know that many of the things it does, (dependency-based setup, sequential logging, etc..) have in fact been done before. There are numerous other ways to start and maintain processes on Linux. All of them are less monolithic and less risky than systemd. One of the biggest technical problems with systemd is the amount of functionality it tries to cram into PID1, which is a special process that really needs to be protected from complex interactions with other code for reliability and security reasons. PID1 is about as close as you can get to the kernel on the OS side without being part of the kernel. There are even kernel modules that are more well-sandboxed away from being able to break the system than PID1.
Many things now have Mono and systemd dependencies, and are therefore possibly subject to patent suits and definitely subject to lock-in problems. The way the open source community typically deals with contentious changes is to fork and let the results of the two forks speak for themselves. The fact that this has been very strongly discouraged and that project leaders have been pressured into accepting Mono and systemd into the mainstream distros is strong evidence, in my opinion, that whomever is responsible for that pressure is up to no good and should be dealt with in a prejudiced manner. Note that I didn't even mention the technical pros and cons of systemd and Mono. Those pros and cons are irrelevant if their presence in mainstream distros enables the torpedoing of the Linux community and related OSS communities. To project leaders who are being faced with pressure to break compatibility with non-Mono or non-systemd systems: a better answer to those pressuring you is: "Go make your own fork."
Realistically, the biggest problem here is that the Linux community has allowed commercial distributions to be the most mainstream ones. This was bound to happen eventually. Luckily, this has left a big opportunity for someone.