You are not logged in.
- Topics: Active | Unanswered
Pages: 1
#1 Re: Off-topic » When you can't tell the difference between Windows and systemd » 2017-09-25 13:01:44
greenjeans wrote:They despise people having any choices, want to further close the source and commercialize linux and give it unremoveable "branding", these people are the very antithesis of everything open-source stands for, and a clear and present danger to free software going forward.
Their fascination with all things from that west coast forbidden fruit company is a dead giveaway. When they show up at a Linux/Open Source conference with their Macbook and then proceed to show Linux running in a VM to show $COOL_FEATURE, it's another dead giveaway that they're not of, by, or for the community. Or, more worrying, they respond to a bug report with, "What's an Xfce?"
They are paid hacks, doing what they're paid to do and trying to pass themselves off as members of the community. There is now a line that must be drawn between the community as we've known it and those who are something else (I'm not sure what to call them). To be sure, I have no problem with being paid to develop Free Software, so long as such software fits the philosophy and spirit of The Unix Way. When it follows some other way, especially in the base system, a user desktop app not so much, then it's time to call its usefulness into question.
I agree with you. I recall that one of them, in a keynote I watched, someone asked if systemd can be removed and replaced with another init. The systemd guy said, no it's Linux and systemd. It's really highly integrated in such a way that you can't manipulate it. Imagine a future where all your essential daemons integrated with systemd, what a nightmare! I can't even understand why an init implements daemons, just why? Are the traditional Unix daemons suck for example? Bffff!
#2 Re: Off-topic » When you can't tell the difference between Windows and systemd » 2017-09-25 12:51:27
I thought that the justification for the vulnerability would be that to install or activate a unit you must be root already, that's why they're not giving it much attention. But imagine having bad behaving software with a root privilege granted by systemd's vulnerability! Your good day systemd.
#3 Off-topic » Linux + systemd, that's not the way we meant to be. » 2017-09-25 09:43:53
- direprobs
- Replies: 0
I really appreciate the efforts that the open source "freedom" community is taking to make the software world free. Free from the dictatorial mindset that many corporations endorse. Devuan by refusing to adapt the complexity of systemd is a revolution facing the mindset in the tech industry. I don't mean by that to ridicule Red Hat guys who worked on systemd, but the systemd invention is rather so complex that a programmer like me got nothing to do except believing in its complexity and idealize those who were behind it. When you use systemd just hope for the best, and try to have your mind wrapped up around the idea that complex "always" implies efficiency.
The argument that XDG files are easier to configure is sound and great. However, there's no simplicity in integrating everything into one thing. systemd is not a failure in my opinion, but a lesson to learn from. Although, I admit that the system is efficient, but what's efficiency when something breaks down in a complex system? You won't be able to help yourself. And this is exactly why I love the idea of freedom in software and not to follow fads in the tech industry. I tend to concentrate on simplicity, I find traditional init systems to be less efficient than systemd or Upstrart, but rather than taking a whole revolution why not try to improve the system if possible? Unfortunately, systemd wanted to revolutionize the whole init system and yet wanted to be part the system which it went against, by being backward compatible with SysV init. I find the idea that systemd tries to be backward compatible to be silly, why? How can you distinguish yourself from others and be them! It's really complicated. If run-levels are trash of the past from systemd's perspective, why have trash next to your door?
Although the XDG files are cool and easy to configure, configuring systemd itself is the real pain. The man pages are ambiguous, and quite often I find myself tinkering to figure out how things fit together. It's a sad reality that behind the beautiful facades there might be pain, traumas, and suffering. I can't even be anything now but wishful that the free open source community will not become the enslaved Open-soft.
Salute to Devuan!
Pages: 1
Board footer
