SystemD
-
I've read the update you made to your original post.
So I now understand your concern is Microsoft control systemd and the proof of that is that the project lead works for Microsoft? Is that the only proof?
I think it's quite a grasp. There is no money in open source so the developers need jobs. In this case the developer happens to be employed by Microsoft.
-
understand what is the common idea about the fact that systemd could be a critical part of Linux which is in the hands of IBM and Microsoft and what this means for the linux community overall.
Either nobody cares, or it's too much complottistic to be real.
I wasn't familiar with the word complotism but yes I think this is correct. It's just a ridiculous conspiracy.
Even if were true that Microsoft had taken over systemd by stealth. What is the harm? If they suddenly do something malicious with it then all the distros will just fork systemd and continue without the malicious elements.
-
That is true, it's open source after all. But i am maybe too old to remember Microsoft strategies to embrace and extinguish... So i am a bit worried, like i was worried that Magisk would be crippled since the lead dev was hired by Google (and indeed, there have been very few progress on Magisk, with Kernel SU getting all the hype lately).
-
I don't even use sudo, so i will certainly not use run0. I have nothing against run0, it make even sense if the footprint is actually smaller than sudo. I was only reporting the article posted on telegram, as i have added a note to the original post, i did not share the view reported in the copied text, but i choose to report it verbatim for clarity.
-
Yes, i hope your view is correct. Indeed he can work for whatever company he likes, but i would see that as a conflict of interest of some kind. Remember also that when you sign up with big tech companies its common that you sell them the intellectual property of all your works, even outside work hours, specially if in the sale related field. Maybe it's not his case, i have no idea.
I was concerned. Maybe i still am a bit. But the fact that systemd can always be forked (or ignored, as that is still possible today) its a comfortable thought.
-
I'm holding out until SystemE comes out
-
Thanks! That's hilarious....
-
In your head, do you say System D or System'd?
-
Sys'Tem'd ? /s
-
Redhat rewrites everything "not invented here" and put these things under "systemd" name.
There are misundestanding between people that have political concerns, and people just happy to get unified shiny things.
If one day Redhat provides a Systemd-OS I'm sure most people will be happy, and will shit on the previous system, with a separated kernel and the freedom of composing your own OS. Most people just wants an open-source Windows and I can understand that.
But I also understand people that are ready to sacrifice some convenience to get a composable OS that can be maintained outside of big companies, thanks to simpler components -
Wrapper?
Wrapper to what?
-
https://github.com/a-schaefers/systemE
SystemE exists
-
Lol this is amazing. Too bad I'm a Vi user so I'll have to port it. All I need is a name.... Hmmm what would make sense for this one...
-
This is one of the most spot-on replies in this thread. Thanks! I think what you wrote is basically correct.
Only people who cares on how the basics is Linux stays compatible and fully free (as in freedom). But that's fine, as far as systemd can be optional.
