3 ms·
People may not trust systemd because years ago there were some really bad defaults like https://github.com/systemd/systemd/issues/2402 https://github.com/system
by deltasquared 3y ago
People may not trust systemd because years ago there were some really bad defaults like https://github.com/systemd/systemd/issues/2402 https://github.com/systemd/systemd/issues/2402 that for instance mounted your firmware in read write mode by default.
That kind of thing leaves a bad taste in some peoples mouth. I am pretty sure some people have bricked hardware with systemd.
- throw0101a 3y agoOr when they started killing user background processes (screen/tmux/nohup X) instead of sending SIGUP like POSIX/Unix has done since basically forever: * https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825941 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825941 As someone who runs mostly servers, I also find resolved annoying and have to rip it out. There's also all sorts of tomfoolery with /etc/resolv.conf in many modern distros, to the point I've taken to setting the immutable flag on it to prevent things diddling with it. There was also the bug where systemD wouldn't allow usernames that started with a number. Poettering's (initial?) response was to tag it as "not-a-bug": > Yes, as you found out "0day" is not a valid username. I wonder which tool permitted you to create it in the first place. Note that not permitting numeric first characters is done on purpose: to avoid ambiguities between numeric UID and textual user names. * https://github.com/systemd/systemd/issues/6237 https://github.com/systemd/systemd/issues/6237 * https://news.ycombinator.com/item?id=14681377 https://news.ycombinator.com/item?id=14681377 (discussion at the time) Nevermind that (a) POSIX allows it, and (b) so do the user manipulation tools of Poettering's employer at the time (RH).