• @[email protected]
    link
    fedilink
    264 hours ago

    I feel like anyone who genuinely has a strong opinion on this and isn’t actively developing something related has too much time on their hands ricing their desktop and needs to get a job

    • @rtxn
      link
      English
      153 hours ago

      My full-time job literally involves dealing with systemd’s crap. There is a raspberry pi that controls all of our signage. Every time it is powered on, systemd gets stuck because it’s trying to mount two separate partitions to the same mount point, whereupon I have to take a keyboard and a ladder, climb up the ceiling, plug in the keyboard, and press Enter to get it to boot. I’ve tried fixing it, but all I did was break it more.

      • @[email protected]
        link
        fedilink
        17
        edit-2
        23 minutes ago

        systemd gets stuck because it’s trying to mount two separate partitions to the same mount point

        Uh… Sounds like it’s not really systemd’s fault, your setup is just terrible.

        I’ve tried fixing it, but all I did was break it more.

        If you’re unable to fix it, maybe get somebody else? Like, this doesn’t sound like it’s an unfixable issue…

        • @jj4211
          link
          61 hour ago

          Uh… Sounds like it’s not really system’s fault, your setup is just terrible.

          I don’t know his specific issue, but the general behavior of systemd going completely nuts when something is a bit ‘off’ in some fashion that is supremely confusing. Sure, there’s a ‘mistake’, but good luck figuring out what that mistake is. It’s just systemd code tends to be awfully picky in obscure ways.

          Then when someone comes along with a change to tolerate or at least provide a more informative error when some “mistake” has been made is frequently met with “no, there’s no sane world where a user should be in that position, so we aren’t going to help them out of that” or “that application does not comply with standard X”, where X is some standard the application developer would have no reason to know exists, and is just something the systemd guys latched onto.

          See the magical privilege escalation where a user beginning with a number got auto-privileges, and Pottering fought fixing it because “usernames should never begin with a number anyway”.

    • @[email protected]
      link
      fedilink
      73 hours ago

      As someone who’s not a developer at all and has been making a comic about systemd for a rather small audience, it’s worse than you think: We actually have stuff to do and procrastinate on them while spending time and thoughts in this, reading old blog posts and forum debates as if deciphering Sumerian epic poems. Many pages were made while I was supposed to be preparing for exams, which I barely passed. Others when I should’ve been cleaning up for moving. I think part of the reason why I haven’t made any in a while is that with a faithful audience being born and waiting for the next chapter, it’s started feeling like something I had to do, and therefore, the type of stuff I procrastinate on.