• mlg@lemmy.world
    link
    fedilink
    English
    arrow-up
    17
    ·
    2 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.

  • juipeltje@lemmy.world
    link
    fedilink
    arrow-up
    24
    ·
    3 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
      ·
      2 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

  • mmmm@sopuli.xyz
    link
    fedilink
    arrow-up
    57
    arrow-down
    1
    ·
    3 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
      link
      fedilink
      arrow-up
      4
      arrow-down
      3
      ·
      edit-2
      3 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
        ·
        3 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.

    • Buffalox@lemmy.world
      link
      fedilink
      arrow-up
      15
      ·
      3 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
    ·
    3 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
      ·
      3 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
      ·
      2 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.

      • printf("%s", name);@piefed.blahaj.zone
        link
        fedilink
        English
        arrow-up
        6
        ·
        2 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.

  • ozymandias117@lemmy.world
    link
    fedilink
    English
    arrow-up
    9
    ·
    3 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