Initially the bug report was shot down by systemd developer Luca Boccassi of Microsoft with:

So an option that is literally documented as saying "all files and directories created by a tmpfiles.d/ entry will be deleted", that you knew nothing about, sounded like a "good idea"? Did you even go and look what tmpfiles.d entries you had beforehand?

Maybe don't just run random commands that you know nothing about, while ignoring what the documentation tells you? Just a thought eh"

Good devs, good product, I’m really excited about our shitty, shitty future.

  • Technus@lemmy.zip
    ·
    3 months ago

    Someone should force this guy to read about the principle of least astonishment.

    Doesn't surprise me that a developer from Microsoft doesn't understand this. To this day, when I select "Update and Shut Down" in Windows, it only actually shuts the computer down about half the time.

  • OpFARv30@lemmy.ml
    ·
    3 months ago

    It's bluca, yo.

    As a random example, here is bluca breaking suspend-then-hibernate, then being a complete asshole about it, while other systemd devs are trying to put the fire out. Do read his code reviews on the latter. yuwata and keszybz have nerves of steel.

    The current behaviour is fully expected and documented

    bluca is cancer.

    • Bitrot@lemmy.sdf.org
      ·
      edit-2
      3 months ago

      He’s trying to be a little Poettering.

      I always think it’s crazy when employees of companies with paying customers act like such jackasses in public.

    • Llituro [he/him, they/them]
      ·
      3 months ago

      Jesus Christ, what a fucking asshole. Calls the very valid complaints "trolling" before locking the fucking thread

    • doeknius_gloek@discuss.tchncs.de
      ·
      3 months ago

      Funny to seem him arguing against HibernateDelaySec because of possible data loss, yet if systemd-tmpfiles purges your fucking home directory it's "documented behaviour". The superiority complex of some people...

  • e8d79@discuss.tchncs.de
    ·
    3 months ago

    Editorializing the title and putting nothing but polemics into the description paints you in a worse light than it does the systemd devs.

  • LalSalaamComrade@lemmy.ml
    ·
    edit-2
    3 months ago

    Just pick a non-systemd distro instead of reinforcing this fear-mongering nonsense editorializing. I can't tolerate corporate stooges putting their dick in our space, so I've switched to Guix. You have a choice, you can switch if you want to - nobody is stopping you. This way, you are also helping the maintainers and the contributors by giving them feedback.

  • fireshell@lemmy.ml
    ·
    3 months ago

    “If you can’t win, lead.” Systemd development is in the hands of Microsoft employees. systemd has taken over almost all of Linux. Experts answer - in whose hands is Linux now? :)

  • poki@discuss.online
    ·
    edit-2
    3 months ago

    Unfortunate. However, one bad move doesn't justify dismissing systemd altogether.

    Do I wish for s6 and dinit to be competitive with systemd? Absolutely. Do I wish for systemd what PipeWire has been for PulseAudio? Yes, please. Do I wish that distros/DEs would be less reliant on systemd? Hell yeah! (Can I please have an rpm-based distro without systemd?)

    But, unfortunately, at least for now, systemd is the most robust and (somehow) most polished init we got. And I'm actually grateful for that.

  • biribiri11@lemmy.ml
    ·
    edit-2
    3 months ago

    The guy replying is a total dick, and for people that like to encourage change to create software that evolves with needs, they sure do refuse to change when needs evolve.

    This is definitely just a dangerous cause of that one xkcd. At the very least, Debian unstable caught something before it could reach everyone else. That works, I guess.