On Wed, 15 Jun 2011, Michael Biebl wrote: > At the current state, I'm not for adding /run/shm to debian-policy. > If we can get wider acceptance of this feature (cross-distro), then my > position > on this might change. Atm this looks like a Debian-only feature with no real > use-case why we need that.
Hmm? The only acceptable access to /dev/shm (and therefore /run/shm) by normal applications is through the SYSV shmem API. Wider distro acceptance is a non-issue. That doesn't mean I think it is a good idea to move it to /run, I think it is a bad idea. IMHO the only interesting use-case for /run/shm seems to be breaking for good any crap that still abuses /dev/shm, which is not nearly enough a good reason to mess with it. I consider storing shm data inside the /run filesystem to be a misfeature (as opposed to having it as a separete tmpfs), so "merging" it with /run is exactly what I'd not like to see happening. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
