• BCsven@lemmy.ca
      link
      fedilink
      arrow-up
      4
      ·
      edit-2
      7 hours ago

      Its a ‘failsafe’ , like if part of the system depends on that drive mounting then if it fails then don’t continue. Not the expected default, but probably made sense at some point. Like if brakes are broken don’t allow starting truck, type failsafe.

      • wormer
        link
        fedilink
        arrow-up
        3
        ·
        7 hours ago

        Yea like the default is smart? How is it supposed to know if that’s critical or not at that point? The alternative is for it to silently fail and wait for something else to break instead of failing gracefully? I feel like I’m growing more and more petty and matching the language of systemd haters but like just think about it for a few minutes???

        • interdimensionalmeme
          link
          fedilink
          arrow-up
          1
          ·
          2 hours ago

          The system failed for no good reason, failing is exactly what it should never ever do. If it had just continued, everything would have been fine.

        • nickwitha_k (he/him)@lemmy.sdf.org
          link
          fedilink
          arrow-up
          1
          ·
          7 hours ago

          the default is smart

          Looking at the systems that are supported, it makes the greatest sense to have the safest failure mode as default. If fault tolerance is available, that can be handled in the entry but, it makes sense but to assume. Having that capability built into the default adds more complexity and reduces support for systems that are not tolerant of a missing mount.

          • wormer
            link
            fedilink
            arrow-up
            2
            ·
            6 hours ago

            Sorry if it looked otherwise, I was agreeing to BCsven. I agree with you