• mmmm@sopuli.xyz
    link
    fedilink
    arrow-up
    61
    arrow-down
    1
    ·
    5 days ago

    You had the chance to call it SystemdOSd and somehow you missed it. My disappointment is immeasurable and my day is ruined.

    Also why aren’t you including the most important piece, systemd-antivirusd?

    • Buffalox@lemmy.world
      cake
      link
      fedilink
      arrow-up
      5
      arrow-down
      3
      ·
      edit-2
      5 days ago

      I have no idea where the antivirus came from?
      OP uses mostly actual examples of Linux functionality.
      I have never used nor needed an antivirus on Linux. And I haven’t heard that systemd should have anything special in that area either.

      • Pommes_für_dein_Balg@feddit.orgOP
        link
        fedilink
        arrow-up
        13
        ·
        5 days ago

        Antivirus in the classical sense is an outdated concept anyway.
        Nowadays, if you want to protect your system, you need endpoint protection that supervises everything with system-level root access and only allows whitelisted processes to run.

  • juipeltje@lemmy.world
    link
    fedilink
    arrow-up
    27
    ·
    5 days ago

    I’d just like to interject for a moment. What you’re refering to as Linux, is in fact Systemd/Linux, or as i’ve recently taken to calling it, Systemd plus Linux.

    • prole@lemmy.blahaj.zone
      link
      fedilink
      arrow-up
      4
      ·
      5 days ago

      Here’s the thing. You said “Systemd/Linux is Linux.”

      Is it in the same family? Yes. No one’s arguing that.

      As someone who is a scientist who studies Linux, I am telling you, specifically…

      Eh fuck it, you get the idea

  • mlg@lemmy.world
    link
    fedilink
    English
    arrow-up
    19
    ·
    5 days ago

    My favorite systemd moment was when Lennart and Kay shouted “systemdeez nutz!” in the kernel mailing list and then proceeded to systemd all over the place.

    • Buffalox@lemmy.world
      cake
      link
      fedilink
      arrow-up
      17
      ·
      5 days ago

      Absolutely, but I guess the joke is that Pulseaudio was also a project headed by Lennart Poettering.
      Pulse was much hated by some, but actually brought substantial improvements to the Linux audio stack at the time.

      The transition to Pipewire however has been amazingly smooth by comparison. I haven’t detected any downsides, and the switch caused zero issues.

  • Saapas@piefed.zip
    link
    fedilink
    English
    arrow-up
    24
    arrow-down
    3
    ·
    5 days ago

    I honestly thought systemd-homed seemed like a pretty sweet idea, last time I heard about it. Of course it was mostly just people screaming how systemd was literally hitler for even suggesting it

    • esc@piefed.social
      link
      fedilink
      English
      arrow-up
      15
      arrow-down
      4
      ·
      5 days ago

      Almost every project under systemd umbrella is great, most distros really underutilize it’s capabilities.

    • black0ut@pawb.social
      link
      fedilink
      arrow-up
      3
      arrow-down
      1
      ·
      5 days ago

      Arch adopted systemd-homed and, at the time, I didn’t even know what it did. But it somehow borked my system. I never needed it, it was added for no reason, and like a lot of systemd features, it broke stuff.

      I’m still salty about systemd-networkd messing up my network. Or about systemd-resolved taking over my custom DNS.

      I have so many systemd packages blacklisted atp, and I don’t even want to. But they keep breaking shit.

      This is just an anecdote and it may not be representative of anything, but that’s my 2 cents.

  • ozymandias117@lemmy.world
    link
    fedilink
    English
    arrow-up
    9
    ·
    5 days ago

    Minor notes, then we can begin implementation

    Only systemd is in PID1, login, journal, etc are their own PIDs

    Surely we’d use pipewired, not pulseaudiod

    Graphics and system ram may be unified, so we need a RAMArbitord that is shared between the main kernel and DRM blocks

      • printf("%s", name);@piefed.blahaj.zone
        link
        fedilink
        English
        arrow-up
        6
        ·
        4 days ago

        Since it’s “open source”, we could start experimenting with our own circuitry, implementing the new Booleand logic: ANDD, ORD, XORD, NOTD and all that good stuff. See if we can tinker together a few instruction setsd.

  • Buffalox@lemmy.world
    cake
    link
    fedilink
    arrow-up
    19
    arrow-down
    10
    ·
    edit-2
    5 days ago

    This post is amusing and funny, but personally I love systemd and I was also very fond of PulseAudio that brought massive improvements at the time.
    Lennart Poettering is absolutely a hero of Linux and Open Source, and helping Linux as a full blown high quality OS get to where it is today. Stronger and better than ever!!! Contrary to other major operating systems that suffer from serious Enshittification.

    Remember before systemd the most popular init system was upstart, and upstart was buggy as hell, with very serious bugs that existed for years without being fixed, because the basic design of init systems made it very very hard (impossible). and upstart was arguably the best among the rest. But because Ubuntu also switched to systemd, upstart has been deprecated because Upstart was an Ubuntu project.

    systemd was an entirely new design strategy that fixed errors that had been impossible to fix with traditional init systems.
    However some still prefer System V init, and I think Gentoo still uses that as default, I suppose because they find it better (easier to use) for tinkerers that micro-control everything.

    But IMO the design of systemd seems like pure genius, really a solution to a problem that needed fixing.

    • prettybunnys@piefed.social
      link
      fedilink
      English
      arrow-up
      14
      arrow-down
      2
      ·
      5 days ago

      I’d wager most folks aren’t even sure why systemd was “controversial” and don’t remember a time before it, but are instead just jumping on systemd implementing age as a field.

      • Buffalox@lemmy.world
        cake
        link
        fedilink
        arrow-up
        5
        arrow-down
        2
        ·
        5 days ago

        A lot of the controversy against systemd was pure bullshit.

        but are instead just jumping on systemd implementing age as a field.

        My guess is you are right, but age verification is not an idea of systemd, implementing it is an attempt at making it possible to fulfill a legal requirement by some countries. It’s stupid, but stupid is now planned to be legally required in some countries.

        • prettybunnys@piefed.social
          link
          fedilink
          English
          arrow-up
          5
          arrow-down
          1
          ·
          5 days ago

          Yep, turns out technology enthusiasts who have a vested interest in an operating system are an opinionated bunch

      • Semperverus@lemmy.world
        link
        fedilink
        English
        arrow-up
        2
        ·
        5 days ago

        Ive been riding SystemD for its faults since the beginning. The age verification was just one more on the pile.

    • corsicanguppy@lemmy.ca
      link
      fedilink
      English
      arrow-up
      4
      ·
      4 days ago

      Remember before systemd the most popular init system was upstart,

      For 5 years; maybe. Before, during, and since, sysV is still the most popular.

      And, as dictionaries, politics and Windows will tell you, what is popular is not always best.

      • Buffalox@lemmy.world
        cake
        link
        fedilink
        arrow-up
        1
        ·
        4 days ago

        Yes upstart was relatively short lived 8 years:

        https://en.wikipedia.org/wiki/Upstart_(software)

        But Ubuntu did put some effort into improving the init process with Upstart, and it was the fastest init system until systemd beat it by being way way better at multi threading.
        Ubuntu also massively improved how well Linux worked on laptops, and upstart was part of that effort too.
        What is best can be subjective, being the most popular signifies that most people found it to be best.

      • Buffalox@lemmy.world
        cake
        link
        fedilink
        arrow-up
        1
        arrow-down
        1
        ·
        5 days ago

        OK thanks apparently OpenRC is a further development of Sysvinit, having many similarities.

        https://en.wikipedia.org/wiki/OpenRC

        Parallel service startup (off by default)

        This is probably because it’s still hard to get to work without handcrafting for a particular system, IMO a very telling difference between the old init designs contrary to systemd that handles parallel startups like a champ.

        • black0ut@pawb.social
          link
          fedilink
          arrow-up
          3
          ·
          5 days ago

          In my experience, booting using single threaded inits (at least in their early stages) actually speeds up the process. The overhead from multithreaded startup on something as simple as an init system can hurt startup performance, especially on older CPUs.

          • Buffalox@lemmy.world
            cake
            link
            fedilink
            arrow-up
            1
            ·
            4 days ago

            Of course you need a CPU capable of multi threading, which today means any CPU, but then there is no doubt that the multithreaded init process is way faster.
            This was thoroughly tested when systemd demonstrated it.
            Single threaded init processes have bottlenecks, and a single issue will stall the whole process. Of course systemd only influence boot speed of user space, but the Linux kernel itself is also multithreaded in it’s boot processes today, because it is without a doubt faster.

    • Semperverus@lemmy.world
      link
      fedilink
      English
      arrow-up
      5
      ·
      5 days ago

      SystemD itself was fine. Not great but better than what we had and I was happy with what it did.

      But then it started to sprawl and take over things it had no business doing.

      At this point I am no longer using the Linux kernel, I’m using the SystemD kernel, and as soon as Poettering feels like it he can simply sell the rights to SystemD to a big corpo like Microsoft once everything fully depends on it.

      • Buffalox@lemmy.world
        cake
        link
        fedilink
        arrow-up
        1
        ·
        5 days ago

        There were pros and cons, I get the annoyance with the binary vs text files.
        But systemd booted faster than upstart, despite upstart was made for speed and systemd was made for being robust. The robustness of systemd however made it possible to make the ini process multithreaded and still work flawlessly, where old ini systems tend to have race conditions that make it near impossible.
        systemd is more robust, faster and more flexible, so how it wasn’t great remains a mystery to me?