The article continues:
"It was described to me by the computer experts I consulted with afterwards that that was purely an attempt to let me know that they could do that, that they were watching, that they were in my computer."
Not saying that interpretation is correct, but it does seem reasonable to point out that she does in fact have a response to your objection.
There's no abuse there. He doesn't say a thing about the presenter personally, just corrects stuff that's in his slide, then says that sometimes what's written on web pages isn't true. Which bit of that did you think was abusive?
It's been running under 'real-world conditions' for years already - do you think no-one runs real-world systems on Fedora, or that Red Hat doesn't run releases in production internally before they go out, or that RH has no customers who test pre-releases?
"Seems to me that's the largest reason it's being pushed"
Nope. I think this impression originally came from Lennart's original post on systemd, years and years ago - http://0pointer.de/blog/projec... - because it starts out talking about boot speed. But even that very first post moves on, in the sections "Keeping Track of Processes" and later, to talk about the really interesting bits of systemd - better service management, and more capable service configuration. As systemd development continued, it's become much more about the latter and much less about boot times - I think that's where Lennart *started* thinking about systemd, but it's really not what systemd is for any more. Red Hat certainly wasn't interested in systemd because it might make servers boot three seconds faster, RH was interested because it can make service management on servers much better.
https://access.redhat.com/docu... is a rather comprehensive and good guide to the changes in RHEL 7 for RHEL sysadmins. One thing you'll learn from it is that RHEL 7 logs to text via rsyslog (as a journald consumer) *by default*.
"anyone sane have to scream NOOOO upon learning it will be Lennart doing the implementation."
Except he isn't.
Because the people doing the damn work to fix it decided systemd was the sensible place to do it. If you'd rather it be somewhere else, why not write it somewhere else?
"The only things I use Linux for anymore is for my personal file server in my basement, and even that is running old Fedora 17."
so...it's running a rather early version of systemd, and apparently working fine, because you haven't seen a need to upgrade it?
"Oh hey, just what I wanted BINARY LOGS THAT BREAK ALL MY EXISTING AUTOMATION."
systemd is designed to make it trivially simple to have text logs if you want that. RHEL 7 is configured by default to do permanent logging in plain text format via rsyslog; the native journald logs aren't even permanently stored by default (this is the config that was in Fedora for a while before journald's native format became the default/primary).
https://access.redhat.com/docu...
I am starting to suspect you're a troll and haven't actually used RHEL 7 at all.
"Systemd by design tries to mount nfs shares, before it even starts up the network, out of the box!"
Um. No it doesn't. Who told you that?
"Systemd supresses everything unless you tell it to."
No it doesn't. Who told you that?
um. what? people have been updating sytems that use systemd for, what, four years now? amazingly enough, it actually works, we don't just all watch our systems crash and reboot every time.
"It does its own logging in binary which needs a tool to read the logs and if it gets corrupted then systemd's devs say "just delete the logs". Really?"
Er...no. They don't say that. journalctl reads as much data as it can from corrupted log files and otherwise routes around them. I don't know of any advice that says to delete them.
journald is also intentionaly designed to make it simple to store logs in plain text format if desired, using rsyslog or something similar as a journal consumer. you can do this alongside or instead of systemd's native log format.
It's one of those things we call "jokes".
Doomed to be buried in
systemd is not about boot time.
If you look at a screenshot of blivet-gui, you'll see it doesn't use the same UI as anaconda.
Anyone can make an omelet with eggs. The trick is to make one with none.
