> Is any of this relevant to yaffs? It looks likely. Yes it is, and I already post it. I will change (today or tomorrow) the patch according to the comment already made on it. > Nick > -------- Original Message -------- > Subject: Exporting jffs2 by nfs with kernel 2.6 > Date: Wed, 6 Sep 2006 17:38:49 +0200 > From: Gregory CLEMENT > To: jffs-dev@axis.com > > Hi all, > > On 2.4.18 we managed to export a jffs2 filesystem by nfs. > Now on 2.6.16 we can't. > I found 2 problems for it: > First, changed was made in nfs, and now they test if > s_export_op is not a void pointer. By dding a pointer on > this structure (even this structure is void) makes nfs happy. > If the structure is void nfs use generic function, so for this part > I think it's ok > > Second, nfs need to identify the filesystem to export. It is done > either by the device of the filesystem or by a "fsid". I didfn't see any > filesystem use a "fsid" and I don't know how to use it. So identification > is made if FS_REQUIRES_DEV is set. The problem was in kernel 2.5.7, > this flag was removed because "We never really used the block device anyway". > Do you mind setting this flag again? Or have you a better idea? > > I joined my patch which make jffs2 exportable by nfs: > > -- > Gregory CLEMENT > Adeneo -- Gregory CLEMENT Adeneo