3 ms·
Did you read the article? The author is complaining that aystemd introduced _optional_ security mechanisms for units. If you don’t like these mechanisms, don’t
by oncallthrow 1y ago
Did you read the article? The author is complaining that aystemd introduced _optional_ security mechanisms for units. If you don’t like these mechanisms, don’t use them in your units.
Systemd didn’t “break” anything at all here. This author’s arcane debugging workflow doesn’t work for certain units who have opted into the new security mechanisms. But that is hardly systemd’s fault.
- cwillu 1y ago“Please don't comment on whether someone read an article. "Did you even read the article? It mentions that" can be shortened to "The article mentions that".” --https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html
- egorfine 1y agosystemd introduced optional timers. Not long time passed and voila - cron is deprecated and hardly works today. systemd introduced optional socket activation. Boom: sshd in process list is faked on Ubuntu 22+. systemd introduced optional structured logging. Voila: every distro now ships with unremovable journald. systemd brand introduced optional systemd-resolved, easily the worst project, and soon it's going to be mandatory for DNS resolution. Whatever systemd makes optional, practically becomes mandatory to use in distros because systemd developers do not code optional things for them to go unnoticed.