From: Dale E. E. <dem...@co...> - 2008-02-09 10:48:21
|
Mrunal, Hi. I had a similar problem in the beginning. Once I sort of understood it, I found a FUSE version of cramfs (I believe it was via the fuse homepage projects). While it is only read-only, it was very similar to what I was working towards and switch to using cramfs as a skeleton project to build my own. Almost nothing remains of the original cramfs, but it is much better than the examples for a disk filesystem. You'll still have to work out a ton of details and open your own FILE pointer to the device etc.... Hope this help get you pointed in the right direction. Dale Mrunal Gawade wrote: > Hi, > > I want to develop a disk based implementation of Log structured file system > on FUSE. I want to keep it as simple as it could be by supporting just the > bare minimum functionality of file creation, write, read, delete. I went > through the existing file systems code but most of it is non-disk based file > system based. I browsed through the disk based file system implementations > but could not get hang of the code in the initial inspection, as its > obtained if a kernel level file system code is observed. I could not > understand role of FUSE and how FUSE could enable me to have lower level > APIs except the normal FUSE functions already supported. > > Could anyone give me some directions about what is the best way to go about > ? I am not comfortable with kernel mode development and needs this prototype > as fast as I could get. > How best is FUSE for disk based file system development? > > > Thank you, > Mrunal > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > fuse-devel mailing list > fus...@li... > https://lists.sourceforge.net/lists/listinfo/fuse-devel > > |