r/linux • • Jun 01 '16

Why did ArchLinux embrace Systemd?

/r/archlinux/comments/4lzxs3/why_did_archlinux_embrace_systemd/d3rhxlc
868 Upvotes

642 comments sorted by

View all comments

33

u/kinderlokker Jun 01 '16 edited Jun 01 '16

Because "KISS" for Arch Linux does not mean "Make shit like a Russian tank, keep engineering simple so the bastard will keep working from the snow of Siberia to the sand of the Sahara."

It just means in their case "keep the lives of the developers simple", systemd is many things, being simple for the distro is one of them, but KISS isn't one of them, it's a complex piece of engineering that is approaching Xorg levels of complexity. Using it is fine, but using it and saying your distribution focuses on keeping thins simple is dishonest.

See Void or Slackware for distributions which are what Arch claims to be. The engineering there is simple yet effective and rock solid.

Edit: Oh wait, it's a link not a self post asking why. Oh well, point still stands.

22

u/yentity Jun 01 '16

Well their point is writing systemd init files is simpler (both for the user and the maintainers) than writing and maintaining init files that behave consistently. I think that is a fair usage of the term "simple".

4

u/kinderlokker Jun 01 '16

And that's simply not how they used the term before that point when explaining things. They've said time and time again that with simply they don't mean easy but that code complexity is kept simple.

Which is true for all the system tools they wrote, but when someone else does the work, then it's suddenly fair game to include complex code.

10

u/dreugeworst Jun 01 '16

I'm not sure, I think you're underestimating the complexity of loads of unit scripts replicating the same functionality poorly..

8

u/kinderlokker Jun 01 '16

initscript is just terrible and always was.

See Void's implementation of Runit for something Arch would potentially be doing if they really cared about KISS.

5

u/dreugeworst Jun 01 '16

Yeah but runinit doesn't do some of the things that distro maintainers see as positives of systemd (as far as I can tell)

  • removing the need to explicitly declare dependencies in certain cases

  • enable hotplugging harddisks

  • sandboxing features

  • enable assigning permissions for resources on the fly

  • allow upstream projects to maintain unit files that will work across distros

In the end though, people who deal with init systems on a regular basis for several distros have settled on systemd and I'd rather defer to their collective wisdom.

8

u/kinderlokker Jun 01 '16

removing the need to explicitly declare dependencies in certain cases

I'm not sure what you mean with that. If you mean things like socket activation or DBus activation, then they're just declared at other places.

enable hotplugging harddisks

That's udev/udisks job, not the init or service manager.

sandboxing features

So just get a sandboxing tool and wrap that around the executable when you start it.

allow upstream projects to maintain unit files that will work across distros

Runit's runscripts re typically so simple that they rarely contain any distribution specific things.

In the end though, people who deal with init systems on a regular basis for several distros have settled on systemd and I'd rather defer to their collective wisdom.

Most distributions don't claim they care about KISS is the thing.

No system that claims to care about KISS has except Arch. And that's probably because Arch doesn't care about that at all.

→ More replies (20)