sag@lemm.ee to Linux@lemmy.ml · edit-21 year agoLinux Directory Structure - FHSlemm.eeimagemessage-square198fedilinkarrow-up11.31Karrow-down157
arrow-up11.25Karrow-down1imageLinux Directory Structure - FHSlemm.eesag@lemm.ee to Linux@lemmy.ml · edit-21 year agomessage-square198fedilink
minus-squarebaseless_discourse@mander.xyzlinkfedilinkarrow-up4·edit-21 year ago/run is a temporary fs, so if the mount, filesystem or even the entire system crashed, all the mounted data will be cleaned up after a reboot. On the contrary, if the mount crashed, it might leave a folder or data on /media, making subsequent mount problematic. Here is a well-written comment about the rationale behind this mount point: https://www.reddit.com/r/linuxquestions/comments/tzo984/comment/i40e2za/
minus-squarecaseyweederman@lemmy.calinkfedilinkarrow-up2·1 year agoProbably so that you don’t accidentally write to a directory by mistake when it isn’t mounted, and then lose access when you mount something over it, all while services are looking for files that are only there sometimes.
minus-squareToribor@corndog.sociallinkfedilinkEnglisharrow-up2·1 year agoI’ve had exactly this happen to me. It was my own fault but it took a bit of work figure out.
What’s the reason?
/run is a temporary fs, so if the mount, filesystem or even the entire system crashed, all the mounted data will be cleaned up after a reboot.
On the contrary, if the mount crashed, it might leave a folder or data on /media, making subsequent mount problematic.
Here is a well-written comment about the rationale behind this mount point: https://www.reddit.com/r/linuxquestions/comments/tzo984/comment/i40e2za/
Probably so that you don’t accidentally write to a directory by mistake when it isn’t mounted, and then lose access when you mount something over it, all while services are looking for files that are only there sometimes.
I’ve had exactly this happen to me. It was my own fault but it took a bit of work figure out.