> Allegedly, it's not just a "change a few lines of code here" job. :-/
Indeed. That was a design decision - and conforms with the way that many other
NFS servers behave.
With unfsd, you can get filehandle conflicts because NFS assumes that all
inodes are on the same device - so the same inode # on different devices can
get the same filehandle.
There was no suitable answer to this problem, so knfsd was declared to be
single-filesystem only. I don't think there's much chance of changing that on
the server side.
When automounting NFS, amd will query the server, and mount all submounts that
are available.
Maybe there should be a mount option which does this for you?
---- ---- ----
David Woodhouse David.Woodhouse@mvhi.com Office: (+44) 1223 810302
Project Leader, Process Information Systems Mobile: (+44) 976 658355
Axiom (Cambridge) Ltd., Swaffham Bulbeck, Cambridge, CB5 0NA, UK.
finger dwmw2@ferret.lmh.ox.ac.uk for PGP key.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/