From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Fawad Lateef" Subject: Re: Regarding a Simple Version of nfs & nfsd Date: Tue, 21 Mar 2006 14:09:21 +0500 Message-ID: <1e62d1370603210109t4910bc59ra817db695ed4c41c@mail.gmail.com> References: <20060320041858.46219.qmail@web37909.mail.mud.yahoo.com> <1142896246.2914.5.camel@ool-44c32f98.dyn.optonline.net> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT Cc: "UZAIR LAKHANI" , linux-fsdevel@vger.kernel.org Return-path: Received: from nproxy.gmail.com ([64.233.182.197]:28796 "EHLO nproxy.gmail.com") by vger.kernel.org with ESMTP id S1751123AbWCUJJY convert rfc822-to-8bit (ORCPT ); Tue, 21 Mar 2006 04:09:24 -0500 Received: by nproxy.gmail.com with SMTP id l37so924672nfc for ; Tue, 21 Mar 2006 01:09:22 -0800 (PST) To: "Avishay Traeger" In-Reply-To: <1142896246.2914.5.camel@ool-44c32f98.dyn.optonline.net> Content-Disposition: inline Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On 3/21/06, Avishay Traeger 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