Anton Aylward wrote:
bruce said the following on 05/06/2013 08:01 AM:
i know /run is a new cross-distribution location for the storage of transient state files, and /var/run is replaced by /run. but 1, why /var/run still have contents just as the same as /run ? just for backward compatibilty ? 3, it seems /var/run is not a symlink to /run, so /var/run occupy harddisk space, just like /run does?
You may be missing something, but I'm not sure what. Try running
ls -li /run /var/run
The "tmpfs" is mounted on both /run and /var/run -- so it is the same memory based file system mounted at both points. That's why you see duplicates in both places -- no symlinks are needed. A mount --bind would do similar, but it's like procfs -- it gets mounted in your root -- but also in every root of every "chroot" instance... but none of them take actual disk space -- just system memory! (which is a darn good reason not to move /tmp to being RAM based, as it gets used for large files sometimes, and .. oops. there goes your memory!...;-) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org