From: bigon@debian.org (Laurent Bigonville) Date: Mon, 14 Jan 2013 14:12:39 +0100 Subject: [refpolicy] [PATCH 07/13] Label var_lock_t as a mountpoint in Debian In-Reply-To: <1358107385.2495.12.camel@d30> References: <1358026351-12955-1-git-send-email-bigon@debian.org> <1358026351-12955-8-git-send-email-bigon@debian.org> <1358107385.2495.12.camel@d30> Message-ID: <20130114141239.4201d733@soldur.bigon.be> To: refpolicy@oss.tresys.com List-Id: refpolicy.oss.tresys.com Le Sun, 13 Jan 2013 21:03:05 +0100, Dominick Grift a ?crit : > On Sun, 2013-01-13 at 19:30 +0100, Sven Vermeulen wrote: > > Is /var/run/lock a (tmpfs) mountpoint, or is /var/run a (tmpfs) > > mountpoint and the lock subdirectory just that - a subdirectory? > > > > I've seen 5 distributions using /var/run as either be a tmpfs, or a > > symlink to /run which is a tmpfs. > > > > > > They both are mountpoints in debian (/run and /run/lock) > > At least that is what i saw from Laurents mount command output Indeed on all the wheezy/sid machines I've running ATM (well that mades 3, but they have been installed at different time), I have (output of mount|grep tmpfs): udev on /dev type devtmpfs (rw,relatime,seclabel,size=10240k,nr_inodes=1016576,mode=755) tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,seclabel,size=814752k,mode=755) tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,rootcontext=system_u:object_r:var_lock_t:s0,seclabel,size=5120k) tmpfs on /run/shm type tmpfs (rw,nosuid,nodev,noexec,relatime,rootcontext=system_u:object_r:tmpfs_t:s0,seclabel,size=1629480k) and (ls -lad /var/*) lrwxrwxrwx. 1 root root 4 oct 19 20:33 /var/run -> /run lrwxrwxrwx. 1 root root 9 oct 19 20:33 /var/lock -> /run/lock Cheers Laurent Bigonville