Fork time? Maybe all the anti-systemd zealots were right all along…

Edit: To address whether it is likely that this change will affect users: Gnome is planning a stronger dependence on userdb, the part of systemd where this change is being implemented. https://blogs.gnome.org/adrianvovk/2025/06/10/gnome-systemd-dependencies/

Final Edit: The PR has been merged into main.

  • jokeyrhyme@lemmy.ml
    link
    fedilink
    English
    arrow-up
    1
    arrow-down
    3
    ·
    2 days ago

    this new anti-systemd sentiment reminds me of anti-TPM and anti-SecureBoot sentiment

    having TPMs and SecureBoot on Linux machines has only ever empowered device owners to ensure that the software on their devices has not been tampered with

    there’s never been a case where these technologies were used against Linux device owners

    likewise, I predict that Linux device owners may find the age field useful for certain opt-in parental controls, but we’ll otherwise look back on this and shrug at the extreme paranoia

    • Soot [any]@hexbear.net
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 day ago

      Is this comment a joke? That or you’re very naive about the problems these things did cause.

      As someone who deals on rare occasion with Linux PCs, both TPMs and Secure Boot have been a fucking PITA that have done nothing but help solidify the Microsoft/Apple/Google grip.

      • jokeyrhyme@lemmy.ml
        link
        fedilink
        English
        arrow-up
        1
        ·
        21 hours ago

        love to hear some examples of the issues you’ve seen

        for years, i’ve always completely wiped the trusted CAs and enrolled my own SecureBoot keys, and only use Linux

        there have been vulnerabilities in SecureBoot, sure, but only for folks that don’t wipe the “trust Microsoft” keys away first

        tell me how user-enrolled keys cements Microsoft’s ownership over my device please :)