> I am writing a small in-memory file system for learning purpose > (https://github.com/pradeep-subrahmanion/taskcachefs). One of the > ideas that came to my mind is to create a file system in which a > process can have its own private space inside the file system like a > sandbox. The process information is included in the inode itself. I > don't know whether this sounds naive . Any comments ? Why do you need to write a filesystem for that matter? You want to work in a chroot environment. For much better use case, explore cgroups (linux containers). -Rajat On Wed, Oct 24, 2012 at 6:28 PM, Pradeep Subrahmanion <pradeep.subrahmanion@xxxxxxxxx> wrote: > > Hi All , > > > I am writing a small in-memory file system for learning purpose > (https://github.com/pradeep-subrahmanion/taskcachefs). One of the > ideas that came to my mind is to create a file system in which a > process can have its own private space inside the file system like a > sandbox. The process information is included in the inode itself. I > don't know whether this sounds naive . Any comments ? > > What are the current available methods to create a file system sandbox > for a process ? > > Thanks , > > Pradeep S > -- > To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
