News for hackers. Stuff that matters.
Re:Why systemd is still divisive after all these years by bcrl on Friday June 19, 2020 @07:39PM (#23580027)
Why does login on a console terminal depend on networking being up? It's a false dependency, one decided upon by the developer of systemd. And it was a poor choice. The mindset that "it's configurable" is inexcusably lame. That mantra allows bad developers to get away with not putting in the work of thinking about and understanding how users experience their software. It also allows rewrite-the-world projects to take off and throw out all the knowledge that is implicitly present in an existing system before having understood why that complexity came to exist in the first place.

Those who do not try to understand history are doomed to repeat it. That has clearly happened in the case of systemd and is why I don't think the attitude it presents towards end users is at the level that such a core piece of infrastructure should display.

Re:Why systemd is still divisive after all these years by SahAssar on Saturday June 20, 2020 @05:07AM (#23582767)
I'm guessing it wasn't the systemd developers that configured it as such, but without seeing your dependency graph and knowing your distro and installed packages I don't know.

Maybe your distro supports LDAP or another remote user directory? Maybe you just have some services installed that depend on the network and that say they are critical to the multi-user.target? You haven't given enough info for me to know, but it probably isn't systemd's fault in this case.

Re:Why systemd is still divisive after all these years by bcrl on Saturday June 20, 2020 @01:46PM (#23585294)
The distro I use is developed by the company that employs the primary systemd developer. Do you really expect me to believe your assertion that he holds no responsibility for how systemd is shipped by that distribution?
Re:Why systemd is still divisive after all these years by SahAssar on Sunday June 21, 2020 @07:59AM (#23591534)
Well, if you used the tools I mentioned you'd know who/what configured your system that way and how to fix it.