• lime!
      link
      fedilink
      English
      135 months ago

      some other init systems just use scripts for config, meaning you can just do whatever

        • lime!
          link
          fedilink
          English
          25 months ago

          a config file can do only what the program that reads it allows. if the program that reads the file is just bash…

        • @[email protected]
          link
          fedilink
          15 months ago

          Limits and constraints are set by the program that reads the config, so no, not whatever. The only way that is a thing, if the program stated that the configs can do whatever, which at that point, is a script.

          Also if a config can do what ever, then most likely that’s a security vulnerability.

  • Phoenixz
    link
    fedilink
    65 months 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

  • mittorn
    link
    fedilink
    75 months ago

    @pewgar_seemsimandroid systemd has a lot of really good things…
    But it’s too complex for init process and even too complex for service manager. Many solib dependencies causes long start, big memory footprint and possibe security issues. Many things might be implemented in some separate services, running with restricted permissions and optionally disabled.
    initng was very similar to systemd, but was very simple and very much faster

  • @[email protected]
    link
    fedilink
    345 months 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.

    • @[email protected]
      link
      fedilink
      315 months ago

      My biggest problem with systemd is that Red Hat has basically used it to push their-way-or-the-highway on many Linux distros. That said, in many situations systemd is better than what came before. Except systemd-networkd. It’s a PITA as far as I’m concerned.

      • Pasta Dental
        link
        fedilink
        185 months ago

        I see why that may not be an ideal position in an ideological sense, where every distro uses the same thing, but i see it the other way around: it’s a way to finally attempt to standardize Linux desktops. Having a standard desktop is crucial for mainstream adoption, because developers won’t bother supporting 4837 different combinations of software. This is the reason I am really excited for the future with flatpak, xdg-portals, systemd, pipewire, Wayland etc etc. This way the distro is no longer the platform, it’s the distro agnostic software stack that becomes the target platform. For example there’s no longer a need to support KDE’s file picker, and gnome’s file picker and xfce’s, you can just call the portal and it will (should) display a file picker. And if the user doesn’t have a supported environment (which the vast majority don’t) then the burden is on them for being different I guess :p

        • @[email protected]
          link
          fedilink
          25 months ago

          The Nix package manager uses systemd for instatiating services for its packages, so you can switch between any setup with one command. Nix will stop and start all the units that were changed. While it’s a Nix feature, systemd is doing all the heavy lifting

        • @[email protected]
          link
          fedilink
          45 months ago

          I like the standardisation of things. I don’t like that it’s glomming over everything to push Red Hat’s way of doing it and slow-walking proposals from other groups.

        • @[email protected]
          link
          fedilink
          35 months ago

          I find it hard to deal with. I generally end up writing a new plan file and just rendering that to networkd.

  • @[email protected]
    link
    fedilink
    415 months ago

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

    • @[email protected]
      link
      fedilink
      English
      25 months 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.

      • @[email protected]
        link
        fedilink
        1
        edit-2
        5 months 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.

      • burgersc12
        link
        fedilink
        English
        25 months ago

        I like the way I can make the timeout 0 so I don’t even need to think about it doing its job :)

        • @[email protected]M
          link
          fedilink
          365 months ago

          I’m pretty sure their arguments boil down to “big company bad” as systemd is developed by Red Hat. Putting a single entity’s products in charge of several basic functions of the computer (like booting, init, daemons, networking) is seen as a bad idea, especially Red Hat which disgraced itself by making the RHEL source code available only to customers (which does not violate the license), but so far I don’t know of any solid evidence of security holes caused by either incompetence or malice.

  • SavvyWolf
    link
    fedilink
    English
    115 months ago

    Anyone got a good tutorial/guide fir SystemD?

    Figure I may as well try to wrap my head around it if it’s supposedly going to murder me in my sleep or whatever.

      • @[email protected]
        link
        fedilink
        English
        7
        edit-2
        5 months ago

        And if you’re not a 50 year-old Linux admin, Arch wiki.

        Edit: don’t be put off by the Arch wiki if you don’t use Arch. 99% of the time, Linux is Linux, and you can follow it for just about anything other than package management.

        • @[email protected]
          link
          fedilink
          15 months ago

          That too but arch wiki sometimes doesn’t list all the possibilities the program can do or not, skill issue if you can’t read.

          • @[email protected]
            link
            fedilink
            English
            1
            edit-2
            5 months ago

            skill issue

            I fully own that. But I like the logical ordering of the page sections on the wiki, and if anything is unclear or info is missing there–which it is pretty rare–I’ll hit up man in desperation

  • Matt
    link
    fedilink
    65 months ago

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

    • @[email protected]
      link
      fedilink
      English
      165 months 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.

  • @[email protected]
    link
    fedilink
    55 months ago

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