/dev/shm
"Alexandre P. Nunes" <[email protected]>
| Newsgroups | gmane.linux.ngpt.devel |
|---|---|
| Message-ID | <[email protected]> |
Hi, I'm just new to ngpt. While trying ngpt-2.0.0, I figure out it requires (well, programs fails to run without) /dev/shm mounted, which I personally don't use. I've found quite a few programs which required it, and patched them to don't do it. I personally don't think a low level library, like ngpt, should. I did not look to the source code with the needed attention, but in a glimpse I think the created file in /dev/shm is them mmap()ed, right? Is there any other trick in it? Because if that's it, there are so many other options, which doesn't rely in mounting filesystems, like anonymous mapping, sysv shm (someone once told me that shmfs was used in his program because sysv shm was converted to shmfs, that is not true, the things aren't related at all). While the later maybe excluded from kernel compilation, anonymous mmap is always there, I guess shared anonymous mapping too. What about a threaded program, let's say a daemon, started right after booting and mounting the rootfs, but before the other filesystems? It may seems weird, but one may want/need to do it. Am I missing some point in here? Another thing is the binary compatibility I posted in forum, does ngpt implements the cancellation point syscall mapping the glibc pthreads have? Thanks, Alexandre