[sf-lug] systemd criticism
Akkana Peck
akkana at shallowsky.com
Tue Aug 26 14:03:27 PDT 2014
Jeff Bragg:
>> I'm sympathetic to the points made here.
>>
>> https://lkml.org/lkml/2014/8/12/459
I think I'm sympathetic, but ... what are the actual points?
I see a lot of flameage, and a lot of namecalling, and no concrete
reasons he hates systemd so much, no details on how it messed up
his system.
It would be a lot more helpful to write about regressions caused by
systemd. Like:
Brian Wood writes:
> I accidentally got a lot of junk in my log file... the same error
> over and over. i tried to find a way to clean out the junk, but
A couple of lines like that contain more detail than Christopher
Barry's whole rant. Or:
> wasn't able to in part because the log was in binary.
Binary logs? Really? Now that's a good concrete argument against
systemd.
I haven't delved into systemd much, and I'm curious to hear about
the good and bad about it. I did fight with upstart quite a bit, and
found it a big step backward from SysV init files -- mostly because
everything was done with undocumented compiled binaries rather than
self-documenting shell scripts, so if you wanted to change anything
about the boot process, you had to download (sometimes quite a lot
of) C source, read it, and maybe rebuild and install it. I gather
that's true of systemd too, and that it affects a lot more of the
system than upstart (more than just boot).
But I haven't hit any actual problems with systemd yet on Jessie
or Sid. So I'm curious to hear what the problems are, and their
workarounds, since I'm sure I'll hit them eventually. "systemd is a
trojan. systemd is a medusa ... groups with agendas ... just don't
believe in freedom" just isn't very enlightening.
...Akkana
More information about the sf-lug
mailing list