Re: nfs-utils 1.0.8-rc1

["J. Bruce Fields" <bfields@fieldses.org>]

On Mon, Dec 19, 2005 at 12:52:48PM +1100, Neil Brown wrote:
> 75 	nor 	P3 	Oth 	bfields@fieldses.org 	NEW 		pseudofilesystem paths are confusing and v3-incompatible
> 
>   That's a fair comment, but the solution isn't obvious.
>   The apparently straight forward approach might be:
>     If 'fsid=0' isn't given in /etc/exports, then auto-export
>       /var/lib/nfs/pseudo-root
>     as fsid=0,ro,... and bind-mount all other exported filesystems
>     into a suitable place in there.

Yes, I've thought about doing something like that.  It has the advantage
that we can fix everything in nfs-utils, without needing new kernel
interfaces.

Another change is needed so that mountd doesn't report that it's
exporting a bunch of paths starting with /var/lib/nfs/pseudo-root.  We'd
need to hide that part of any such path from the mount protocol
entirely--so the export

	/var/lib/nfs/pseudo-root/path

would be referred to as "/path" for the purposes of mount requests and
responses.

Should we start coding all this?  I'm a little nervous about making
exportfs suddenly do a bunch of bind mounts behind the administrators
back, but I guess we can control that behaviour with configuration
and/or commandline operations and let administrators and users decide
how to handle the transition.

--b.


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs