Comments by "Lawrence D’Oliveiro" (@lawrencedoliveiro9104) on "Systemd Haters Getting Their Panties In A Twist" video.

  1. “Have you tried turning it off and on again?” Or if that fails, reinstall ...
    5
  2. The only example I could think of where Pöttering and mates blamed other people’s mistakes was to do with the fstab issue, where some distros would allow booting to continue with missing volumes. There are “noauto” and “nofail” options that you are supposed to use to make these volumes optional, which they were not using. So along comes systemd and enforces the requirement for these long-documented options, and suddenly incorrect configurations that were successfully booting before would now hang. And so systemd got the blame.
    3
  3. “Comments are disabled for this video” ... tells you everything you need to know about the content.
    3
  4.  @mitchelvalentino1569  Gee, I wonder why ...
    3
  5. That McIlroy quote was only ever a half-truth. Look at any Linux system, and you will see big pieces without which the small ones would never work: the kernel, the X server, bash, even glibc, just to name a few.
    2
  6. I like the service template feature. I currently use it to manage multiple OpenVPN connections into my office. Another nice feature is the randomized delay option on timers. So unlike cron where you have a whole bunch of periodic tasks kicking off at the same time and peaking your system resource usage, you can have them automatically spread themselves around a little, evening out the load.
    1
  7. systemd is a collection of pieces, not one monolithic piece. It is no more a SPOF than pid 1 was always a SPOF -- kill that, and your system died.
    1