• Possibly linux
    link
    fedilink
    English
    arrow-up
    9
    arrow-down
    10
    ·
    3 months ago

    You could just use systemd mounts like a normal person. Fstab is for critical partitions

    • renzev@lemmy.worldOP
      link
      fedilink
      English
      arrow-up
      22
      arrow-down
      2
      ·
      3 months ago

      Fstab is for critical partitions

      Hush everyone, don’t tell this guy about noauto, it’ll burst his bubble

        • InverseParallax@lemmy.world
          link
          fedilink
          English
          arrow-up
          8
          ·
          3 months ago

          Jesus, I mount everything manually from noauto, except root.

          If nfs isn’t available, I don’t want my system to hang, typing mount takes 2 seconds.

          • Possibly linux
            link
            fedilink
            English
            arrow-up
            2
            arrow-down
            2
            ·
            edit-2
            3 months ago

            Wouldn’t your NFS not mount in that case? Wouldn’t you want it to retry periodically? Also, what happens to your service when NFS isn’t available?

            Sounds like systemd mounts are better in this case (unless the device is non critical)

            • InverseParallax@lemmy.world
              link
              fedilink
              English
              arrow-up
              4
              ·
              3 months ago

              I mount it manually when I’m sure everything is up.

              The issue is, I use this workstation to bring up the rest of my network and servers if they’re down, can’t have a hard dependency on nfs if it’s job is to bring up nfs.

    • qjkxbmwvz@startrek.website
      link
      fedilink
      arrow-up
      9
      arrow-down
      1
      ·
      edit-2
      3 months ago

      This happened to me when Debian switched from SysV to systemd. I am not the only person who experienced this (e.g., https://bbs.archlinux.org/viewtopic.php?id=147478 ).

      This is not to say the systemd behavior is wrong, but it essentially changed the behavior of fstab. Whether this is Debian’s fault, Arch’s fault (per the above link), systemd’s fault, or my fault is a fair question. But this committed that most egregious of sins per our Lord and Savior Torvalds — it broke my userspace.

      • Possibly linux
        link
        fedilink
        English
        arrow-up
        5
        arrow-down
        9
        ·
        3 months ago

        That was a really long time ago. (2015) I don’t understand why you are holding a grudge for almost 10 years. Most people have never used a system without systemd.