Systemd Creator Lands at Microsoft • Hacker News Board

Re: Systemd Creator Lands at Microsoft

#21

Post by m-p-3 » Mon, Jul 18, 2022, 12:54 AM UTC

alex3305 wrote: post #8

SahAssar wrote: post #5

> The general perception is that no one wants it (systemd) I disagree. A few loud voices strongly do not want it, but a few others like it, and the vast majority seems pretty content using it, not caring as long as it works well enough.

I'm only using systemd as a user, but for me the overall experience is rather painless after some trial and error. Except the learning curve for more advanced usages is steep and documentation seems way too complete and complicated. But I tend to experience that more with (larger) open source projects anyway, so maybe that's on me.

Same here. I can't say I'm comfortable with it, but for the amount of services I manually need to create (that aren't pre-made by package maintainers) I normally find enough info online to figure it out by myself.

Re: Systemd Creator Lands at Microsoft

#22

Post by cassianoleal » Tue, Jul 19, 2022, 1:53 PM UTC

SahAssar wrote: post #19

cassianoleal wrote: post #17

Earlier quoted context omitted.

I like systemd's service units and its subsystem, and related units like sockets. I dislike pretty much everything else about it.

What "else" are you referring to? networkd? resolved? journald? Something else?

All of those, yes.

Networkd is a pain to configure and operate, and interferes with the lower level subsystems. Resolved is a mess that only causes headaches. It might be ok-ish on desktops but honestly I never had an issue with regular /etc/resolv.conf on any of my laptops and desktops. Journald is a (terrible) solution looking for a problem and makes everything more opaque and harder to troubleshoot.

Containerisation and namespacing is a big mess and lacking on basic features. It also doesn't play nice with the core tooling (ip netns, etc).

I like the service units but honestly we could all have done without it. There were already other perfectly usable solutions in that space. I used runit for a while before nearly every distro out there caved to systemd.

Re: Systemd Creator Lands at Microsoft

#23

Post by SahAssar » Wed, Jul 20, 2022, 9:39 AM UTC

cassianoleal wrote: post #22

SahAssar wrote: post #19

Earlier quoted context omitted.

What "else" are you referring to? networkd? resolved? journald? Something else?

All of those, yes. Networkd is a pain to configure and operate, and interferes with the lower level subsystems. Resolved is a mess that only causes headaches. It might be ok-ish on desktops but honestly I never had an issue with regular /etc/resolv.conf on any of my laptops and desktops. Journald is a (terrible) solution looking for a problem and makes everything more opaque and harder to troubleshoot. Containerisati…

Alright, gotcha. They have all worked well for me, but I understand that they might not for you. The good thing then is that all of those are replaceable with their traditional counterparts, so you can pick and choose while still keeping the core systemd that you seem to find acceptable.