Date: Sun, 1 Sep 2013 17:45:48 +0400 From: Vasily Kulikov <segoon@...nwall.com> To: musl@...ts.openwall.com Subject: Re: Initial draft of musl documentation/manual On Sun, Sep 01, 2013 at 00:41 -0400, Rich Felker wrote: > ### Filesystem Layout Dependencies > > musl aims to avoid imposing filesystem policy; however, the following > minimal set of filesystems dependencies must be met in order for > programs using musl to function correctly: > > * `/dev/null` - required by POSIX > > * `/tmp` - required by POSIX to exist as a directory, and used by > various temporary file creation functions. > > * `/dev/shm` - must be a directory, and should have permissions 01777. > If absent, POSIX shared memory and named semaphore interfaces will > fail; programs not using these features will be unaffected. If you name such files which are important in case of specific API usage and are not needed if this API is not used, why not enumerate other files like: /dev/ptmx /dev/pts/* /dev/tty Or, even better, compile two lists. The first is a list of files which are needed for sure to be able just to start executable compiled against musl, and a list of should-have files which are needed for several non-critical APIs like POSIX shared memory stuff. Thanks, -- Vasily Kulikov http://www.openwall.com - bringing security into open computing environments
Powered by blists - more mailing lists
Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.