• afb@lemmy.world
    35·
    5 days ago

    I don’t hate systemd, but I prefer OpenRC and usually use it on my Debian systems. My preference is purely vibes based though, and I think most of the anti-systemd arguments in common usage are a bit silly.

  • Kusimulkku@lemm.ee
    32·
    5 days ago

    Systemd-boot and the service files and timers are pretty neat. Works fine as an init too I guess

    • wabasso@lemmy.caEnglish
      2·
      4 days ago

      Those are the features I’m most interested in. Do you have a tutorial / resource you can recommend?

      The man pages are, as with most Linux, technically sufficient. Just very hard to digest if I don’t have four hours of interrupted time.

      • vinyl@lemmy.world
        1·
        4 days ago

        From experience when I look for something “easier to digest” I end up spending more time tinkering and fucking about than just reading the man pages because the latter usually had a lot more context about the software and any other weird quirks.

  • somegeek@programming.dev
    151·
    4 days ago

    SystemD works great, but the corporations and politics behind it will ruin Linux if they fully take over. They are already optimizing heavily for IoT just because IBM is heavily focused on IoT

    • FooBarrington@lemmy.world
      41·
      4 days ago

      I’m pretty sure IBM hasn’t focussed on IoT in a long time

      (In the sense that I used to work there and know they’ve both reduced investment in, and fully removed, some parts of their portfolio regarding IoT)

      • somegeek@programming.dev
        25·
        4 days ago

        Just search IBM IoT and look at IBM acquisitions in the last decade.

        Everyone “used to work for that company” on the internet. And even if you used to work there it doesn’t mean you know anything about their business. IBM is more of a Holding now. Like Volkswagen. Just because someone works at audi it doesn’t mean they know anything about Lamborghini.

        https://unixdigest.com/articles/the-real-motivation-behind-systemd.html

        • FooBarrington@lemmy.world
          11·
          4 days ago

          I’m well aware of IBM IoT and their acquisitions, but I’m also aware that most of that stuff happened around 2016-2018, and since then that part of the business has been shrunk down and sold off.

          Believe what you want. I did work in IBM IoT, but what do I know ¯\_(ツ)_/¯

          If you read your own article, you’ll also notice that it doesn’t mention IoT even once. It talks about embedded use cases, which is not the same as IoT. Are you sure you’re not just throwing together unrelated topics?

  • Tja@programming.dev
    5·
    4 days ago

    I dislike journalctl more than systemd. And I don’t get what’s the advantage of systemctl vs previous solutions, why would that of all things make one reconsider.

    I miss rc.local and crontabs. Now if you excuse me I have a cloud to yell at.

    • Hawke@lemmy.world
      3·
      4 days ago

      The only advantage I see is that it actually seems to keep a better handle on the status of the process/service. The old-style unit scripts would often get out of sync and not realize that a process had died, or if they did they would repeatedly respawn a service that would just die again. Maybe that was less of a problem in later years than I experienced earlier, but it was there.

      The whole init.d system felt very ad-hoc with every script working a little bit differently, giving different output styles, etc.

  • Matt@lemmy.ml
    6·
    4 days ago

    Try to pass init=<path to any other init system> and you’ll see reduced RAM usage. Systemd is bloated.

    • azertyfun@sh.itjust.worksEnglish
      13·
      4 days ago

      Hell, pass init=/bin/yes and you’ll see even more greatly reduced RAM usage!

      ❯ ps aux | grep /usr/lib/sys | awk '{print $6}' | sed 's/$/+/' | tr -d '\n' | sed 's/+$/\n/' | bc
266516

      So that’s 260 MiB of RSS (assuming no shared libs which is certainly false) for:

      • Daemon manager
      • Syslog daemon
      • DNS daemon (which I need and would have to replace with dnsmasq if it did not exist)
      • udev daemon
      • network daemon
      • login daemon
      • VM daemon (ever hear of the principle of least privilege?)
      • user daemon manager (I STG anyone who writes a user daemon by doing nohup & needs to be fired into the sun. pkill is not the tool I should have to use to manage my user’s daemons)

      For comparison the web page I’m writing this on uses 117 MiB, about half. I’ll very gladly make the tradeoff of two sh.itjust.works tabs for one systemd suite. Or did you send that comment using curl because web browsers are bloated?

      For another comparison 200 MiB of RAM is less than two dollars at current prices. I don’t value my time so low that I’ll avoid spending two bucks by spend hours debugging whatever bash scripting spaghetti hell other init systems cling onto to avoid “bloat”. I’ve done it, don’t miss it.

  • daggermoon@lemmy.world
    3·
    4 days ago

    I’ve used both runnit and systemD and I prefer systemD. Nothing against runnit and I love Void Linux.

  • neox_@sh.itjust.worksFrançais
    3·
    4 days ago

    Well, I think that if declarative configuration is what you’re looking for, the GNU Guix distro with its GNU Shepherd init system might be a more pertinent solution than SystemD

  • Phoenixz@lemmy.ca
    63·
    4 days ago

    Journald can pound a bag of dicks, it’s the worst.

    After a decade of justified hatred against systemd and avoiding it whenever I can I finally found a reason why I might start using it, so I will

    Still doesn’t mean that systemd is not bloatware with some horrible features built by a horrible main developer