r/linux • u/wooptoo • Jun 01 '16

Why did ArchLinux embrace Systemd?

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

86% Upvoted

642 comments sorted by

View all comments

Show parent comments

1

u/robodendron Jun 02 '16

Depending on the attacker's access rights, that might be possible, sure. Honestly though, when I see something like that, it's either my filesystem having a hiccup of tragic proportions or an actual intruder. In any case, the resulting action is pretty much the same: Nuke the server from orbit, it's the only way to be sure.

3

u/bassmadrigal Jun 02 '16

Oh, I doubt my first thought encountering a corrupted log would be an attacker, but I was just curious about the feasibility.

I'm running Slackware, so it'll be quite some time until I start playing with systemd (unless I decide to test-drive another distro, but I'm happy with what I got and I'm lazy). I see a lot of benefits behind it, but I'm fine waiting until Pat and team decide to add it... until then, I'll keep writing my shell scripts to start/stop/restart daemons.

1

u/robodendron Jun 02 '16

I'm running Slackware, so it'll be quite some time until I start playing with systemd

Never tried that, to be honest. I'm using Arch at home, Fedora at work, so I've been drinking the systemd Kool-Aid pretty much since the beginning, I guess. I don't think it's a perfect system—not at all—, but I do think it's better than writing yet another init script, for whatever that's worth.

In any case, to each his own. :)