you are viewing a single comment's thread
view the rest of the comments
[–] -1 points 2 years ago (2 children)

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

  • source
  • parent
  • hideshow 4 child comments
  • [–] [S] 20 points 2 years ago (1 child)

    Fstab is for critical partitions

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

  • source
  • parent
  • hideshow 2 child comments
  • [–] -2 points 2 years ago (1 child)

    I've never seen it used in the wild

  • source
  • parent
  • hideshow 2 child comments
  • [–] 8 points 2 years ago (1 child)

    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.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 0 points 2 years ago* (1 child)

    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)

  • source
  • parent
  • hideshow 2 child comments
  • [–] 8 points 2 years ago* (1 child)

    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.

  • source
  • parent
  • hideshow 2 child comments