News for hackers. Stuff that matters.
Re:System Down: A systemd-journald exploit by insertcredit on Thursday January 10, 2019 @11:32AM (#18875111)
At least as far as Debian is concerned, you will find that the people with skin-in-the-game (administrators) were massively against systemd. The Devuan fork/split happened exactly because of that.
Re:System Down: A systemd-journald exploit by amyjess on Thursday January 10, 2019 @02:27PM (#18877150)
> you will find that the people with skin-in-the-game (administrators) were massively against systemd

Let me offer you an anecdote from my company. Now, we're a RHEL shop and not a Debian shop, but we've been around since long before systemd.

Most of our hosts now run RHEL 7, but we still have a handful of old boxen still running RHEL 6, and I've been personally involved with quite a few migrations from RHEL 6 to 7 during my time here. Whenever we retire a RHEL 6 host and replace it when a RHEL 7 host, the general consensus from the people who administrate it is "thank god we can now use systemd instead of having to deal with sysvinit". Every time I have to do anything on one of our remaining RHEL 6 hosts, I brace myself for pain, because our RHEL 7 hosts are just that much easier to manage.

Re:System Down: A systemd-journald exploit by kasabali on Friday January 11, 2019 @04:35AM (#18882062)
RHEL 6 was using upstart, not sysvinit, so the general consensus of the people you mentioned is irrelevant.
Re:System Down: A systemd-journald exploit by jamespo on Thursday January 10, 2019 @01:03PM (#18876221)
That's because they only understand bash and not c
Re:System Down: A systemd-journald exploit by geggam on Thursday January 10, 2019 @01:25PM (#18876446)
because configuring and managing systems in C seems suboptimal ?