3 ms·
Aren't we just a few weeks after Rich Hickey's "you have no right to make demands of open source software" rant? Systemd has responsibility that no other userl
by jodrellblank 8y ago
Aren't we just a few weeks after Rich Hickey's "you have no right to make demands of open source software" rant?
Systemd has responsibility that no other userland system has. It's PID 1.
No, you have the responsibility to check what the software you are installing does, and if you don't approve, change it or reject it. Or, don't check, and deal with it.
Systemd developers do not owe you working POSIX, working cron, industry wide working Linux automation, screen, separate userland for everything. They don't owe you anything. If you don't like their thing, don't use their thing.
- buster 8y agoAlthough I very much like the "don't break userland" approach, I agree with you. Especially in the light, that 1. You can start your background process the systemd way (shown elsewhere in this thread) 2. You can configure the desired behavior 3. Your distro probably already has configured it for you (Debian) So it comes down to "something changed which is absolutely extremely important for me but I would rather discuss about it for hours then take the few seconds to configure it". Especially since the new behavior is intended behavior and also has upsides for a lot of use cases. So don't be ungrateful. Be happy that some people are really putting a lot of work behind the software you use daily FOR FREE and just configure the darn thing the way you like. And last but not least, most people here (me included) are not in the position to complain so much about free software, unless they show some commitment to open source themselves.
- deleted 8y ago[deleted]
- Karunamon 8y ago>If you don’t like their thing, don’t use their thing Oh how I wish that was a course of action I could reasonably take in this instance...