From: Chris Friesen on 17 May 2010 13:02 On 05/17/2010 10:36 AM, Casper H.S. Dik wrote: > Chris Friesen <cbf123(a)mail.usask.ca> writes: >> It is not true that it "can't" have such a location. The spec doesn't >> mandate a storage location, but it doesn't say that they are forbidden >> either. A conforming implementation could specify a storage location >> for private mappings should it wish to do so. > > Ah, but it is *private* so it is clearly it cannot be in the filesystem > space. Sure it can. Nothing says that the filesystem space has to be global. It would be relatively straightforward to implement this using per-process filesystem namespaces. Linux could do this now if anyone wanted to do it. Chris
First
|
Prev
|
Pages: 1 2 Prev: New functional language - Fling Next: tutorial or guide to terminal settings? |