Unix grey beard here.
Yes. Distros with systemd are simply easier to maintain.
Even when DNS resolution isn’t working properly?
Especially then. Great documentation and support tooling make troubleshooting much easier.
Can you give me a link to that documenation and tooling? Because every time I go to troubleshoot an issue, I end up in a tangled mess of trying to figure out how systemd and NetworkManager have decided to configure themselves on this particular system, and I give up.
I don’t know how it happens, but I can set up Ubuntu on a dozen laptops in exactly the same way, and a week later they all have different configurations.
Can you give me a link to that documenation and tooling?
Linux daemons and utilities typically come with manuals that get installed alongside the software. There’s a command line tool, aptly called
man, that can be used to search and display these manuals. So for instance,man resolvectldisplays the manual for the command line utility that you can use to control, configure, monitor and debug thesystemd-resolveddaemon. (Although I usually look up the man page online because it’s more convenient to scroll through than in a terminal.) Man pages for a given daemon will typically mention near the bottom related man pages for e.g. control utilities likeresolvectl, so it’s not necessary to remember it by heart.a week later they all have different configurations.
I’m trying to remember any situation where one of the systemd components would change its configuration on its own, but I’m coming up blank. It may be my memory failing me, but possibly that’s the wrong tree to bark up?
Arch wiki ftw
Never had a systemd caused DNS issue.
Then I must be using it wrong. I kept systemd-resolved on my laptop but on my desktop I use plain old
/etc/resolv.conf
You won’t ever get me to care about what init system I run on my machine. I just need it to work.
Exactly. There are more important holy wars and bigger hills to die on.
Sounds like something an Emacs user would say
The comments in here are going to be normal
Upstart was perfect!
I agree. For a init system.
I don’t like the “takeover” of network and home folders. (It feels like a takeover for me)
When I was starting to use Linux in the late 2010s, I was quite confused by how all the init stuff worked. Now that I use NixOS and systemd, I’m things have become really easy. I could write a simple backup system by chaining a few services together without problems.
Might it be, that you have also learned a bit here and there?
[disputed]
Systemd is fine but I am kinda sad that it’s ubiquity has resulted in increasing dependence on it.
I really like void linux which uses runit and it seems like its getting harder for things to work without systemd. Gnome made some changes fairly recently that increase dependence, I hope devs can build ways for gnome to still work :/
My only real criticism is that using runit makes me feel like systemd could be a lot smaller and more elegant. But using systemd has never caused me any problems as best I’m aware 🤷♂️
The first thing forcing an option does, is depriving that option the ability to know what it could achieve on pure merit.
No one cares about systemd at this point
If you want to use your computer like it is 2005 go for it. Just don’t keep bringing up this dead topic.
Where did all the Pöttering hate go?
