On Sun, 2007-01-07 at 17:36 -0500, David H. Lynch Jr. wrote: > I am trying to write a vfs driver for a fairly simple filesystem. > > I have been looking for a good sample to start from an most of what > I have seen is either too simple or too complex. > > I do not need subdirectories, hard links, symbolic links, ACL's. I > am supporting an existing ROM filesystem that > has no superblock, Files start with a directory header that has the > filename and other attributes as text strings, > the header is followed by the file data. The data runs contiguously > until the end of file and is then 0xff filled to the next > 2000h boundary. > > I already have a working mtd block device to access the ROM > (actually write protected flash) > > I am looking for something really simple to start from, but also > something that actually uses an underlying block device. > All the "tutorial" examples I have tripped over (rkfs, ols2006 > samplefs) seem to impliment in memory filesystems - unless I > am mis-understanding how VFS to block device mapping works.
You may want to look at cramfs (fs/cramfs), which is a read-only file system that doesn't have much code to it. Avishay - To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
