Re: Regarding a Simple Version of nfs & nfsd

["Fawad Lateef" <fawadlateef@gmail.com>]

On 3/21/06, Avishay Traeger <atraeger@cs.sunysb.edu> wrote:
> On Sun, 2006-03-19 at 20:18 -0800, UZAIR LAKHANI wrote:
> > I myself want to write a network file system. I want
> > to find out how I can get the simplest version of nfs
> > and nfsd that implements the simplest file system
> > actions without any other features like the security
> > issues.
> >
> > I want this type of nfs and nfsd code as to get the
> > help about how the file system routines are handled in
> > a network environment.
> >
> > Upto now I am using Wrapfs (a wrapper file system)
> > code by Erez Zadok. That is I mount wrapfs on a mount
> > point and the read/write on the mount point will
> > actually be read/write on the underlying file system.
> >
> > I want to extend this idea in to a network file sytem
> > i.e. the client does nothing but trasfers the
> > read/write request to the server which does the actual
> > read/write.
>
> I don't think that you can implement NFS using a stackable file system.
> A stackable file system sits between the VFS and a regular file system.
> The stackable file system can change data, operations, etc. before
> calling the lower level file system methods.  However, they cannot
> change the transport method.
>

I think stackable file system can be used as the server side daemon
with network communication support (somewhat like nfsd) which controls
the underlying file system (which can be any other normal fs) and as
far as client is concern it can act like a complete file system which
actually does nothing by it-self rather get data from the stackable fs
on the server (somewhat like nfs), so the client/user can use that
filesystem to mount the server filesystem. (I think Avishay this is
what Uzair wants to ask)


--
Fawad Lateef