vfsx17.patch available - continuing vfs work (expert developers only)

Simon 'corecode' Schubert corecode at fs.ei.tum.de
Fri Nov 5 05:59:12 PST 2004

On 05.11.2004, at 11:44, YONETANI Tomokazu wrote:
    The next patch is ready.  I haven't dealt with the nfs server, 
    or nullfs yet, I've been working around the edges cleaning things 

	fetch http://leaf.dragonflybsd.org/~dillon/vfsx17.patch
I'm running make -j100 buildworld with /usr/obj NFS-lookback mounted
from /home/nfs to see if it survives (the previous one didn't finish).
I'll run other benchmarks on that mount point if it's finished.
One thing I noticed is that, with the following line in /etc/exports
(and is mounted to /usr/obj) one would usually get `permision denied'
(unless you specified one of -map* options) if you for example try to 
a file on the NFS mounted filesystem as root; with vfsx17.patch, it 
a file with uid = 4294967296 instead.  Is this normal?
If I understand correctly, this is about the same I always (ot not) 
expected to happen: default root mount to nobody.

\ /
 \     ASCII Ribbon Campaign
/ \  Against HTML Mail and News
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pgp00001.pgp
Type: application/octet-stream
Size: 186 bytes
Desc: "Description: This is a digitally signed message part"
URL: <http://lists.dragonflybsd.org/pipermail/kernel/attachments/20041105/2124e111/attachment-0020.obj>

More information about the Kernel mailing list