Re: tmpfs != /dev/shm (was Re: noexec on /dev/shm)

2010-12-23 Thread Lennart Poettering
On Wed, 15.12.10 08:44, John Reiser (jrei...@bitwagon.com) wrote: > > I don't think there's a particularly good reason to use that filesystem for > > other uses. Just mount another tmpfs elsewhere. > > mount() requires CAP_SYS_ADMIN and therefore an application cannot rely > on performing mounts.

Re: tmpfs != /dev/shm (was Re: noexec on /dev/shm)

2010-12-15 Thread John Reiser
On 12/15/2010 06:40 AM, Matthew Miller wrote: > On Tue, Dec 14, 2010 at 10:19:38PM -0800, John Reiser wrote: >> Also, the claim "The API for /dev/shm is shm_open()" is incorrect. >> See the other message for the history. When something is in the file >> system, then by default the file system APIs

tmpfs != /dev/shm (was Re: noexec on /dev/shm)

2010-12-15 Thread Matthew Miller
On Tue, Dec 14, 2010 at 10:19:38PM -0800, John Reiser wrote: > Also, the claim "The API for /dev/shm is shm_open()" is incorrect. > See the other message for the history. When something is in the file > system, then by default the file system APIs (including creat, open, > read, write, close, exec