5 ms·

One of my earliest experiences with systemd's binary log files was on an embedded system I had chrooted systemd-nspawned into, and every time I tried to get

One of my earliest experiences with systemd's binary log files was on an embedded system I had ~~chrooted~~ systemd-nspawned into, and every time I tried to get the log output it would segfault (some issue with qemu-static probably). Very frustrating experience. Really feels like "Embrace, extend, extinguish" but the thing they're extinguishing is unix-as-a-programming-environemnt.

sliken 4y ago
Or a Redhat plan to generate more consulting/support income. Ever wonder why Oracle products were so hard to install/maintain?
- egberts1 4y ago
  It's the IBM way. Everything be in 4-digit or 5-digit error code. Need to RTFM for such codes. Or worse, StackOverflow them.
- yawaramin 4y ago
  Yes, a for-profit corporation has the nefarious plan to... checks notes ...try to earn more revenues. We certainly can't stand for that!
  - sliken 4y ago
    Heh, well making your product worse for more revenue seems pretty warped, and increases the risk of lost market share. Even more warped is having 2 of your engineers join the Debian technical committee and use the bylaws to force a vote before anyone figures out exactly what SystemD is.
    - deleted 4y ago
      [deleted]
    - yawaramin 4y ago
      Were they coerced to vote for it? Why did they vote for it if they didn't know what it is? Honestly it's hilarious how systemd haters see conspiracies everywhere.
a1369209993 4y ago
- kaba0 4y ago
  That's an ultra dumb take. It is a fking trivial binary format with an open spec, which is not particularly complicated. Is linux also EEE? Because those ELF files are quite a bit more difficult to decypher...
  - traverseda 4y ago
    > Is linux also EEE? Oh yes, quite intentionally. See also "viral" licenses like the GPL.