All of lore.kernel.org
 help / color / mirror / Atom feed
From: "David H. Lynch Jr." <dhlii@dlasys.net>
To: linux-fsdevel@vger.kernel.org
Subject: Writing a VFS driver
Date: Sun, 07 Jan 2007 17:36:48 -0500	[thread overview]
Message-ID: <45A17600.6090004@dlasys.net> (raw)

    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.

-- 
Dave Lynch 					  	    DLA Systems
Software Development:  				         Embedded Linux
717.627.3770 	       dhlii@dlasys.net 	  http://www.dlasys.net
fax: 1.253.369.9244 			           Cell: 1.717.587.7774
Over 25 years' experience in platforms, languages, and technologies too numerous to list.

"Any intelligent fool can make things bigger and more complex... It takes a touch of genius - and a lot of courage to move in the opposite direction."
Albert Einstein


             reply	other threads:[~2007-01-07 22:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-07 22:36 David H. Lynch Jr. [this message]
2007-01-07 23:28 ` Writing a VFS driver Avishay Traeger
2007-01-08  3:23   ` Phillip Lougher

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=45A17600.6090004@dlasys.net \
    --to=dhlii@dlasys.net \
    --cc=linux-fsdevel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.