> At least from looking at the Linux 2.2.18 code, if you get EROFS back
> from the Linux server, the actual set of access bits you get back won't
> have the right bits set; "nfsd_access()" just jumps to "out:" if it gets
> a "read-only file system" error, and that doesn't set "*access" to the
> result.
Oh. "Joy".
> If you do want to work around the Linux bug, you'd probably have to send
> another ACCESS request over the wire, with the write bits turned off;
> I'm not sure whether that's worth the effort or not.
Based on that; no. I think if people want to run v3 against a Linux
server, they will just have to turn the ACCESS cache off. In the
meantime, is there any constructive way we can encourage the Linux NFS
folks to fix this behaviour?
--
... every activity meets with opposition, everyone who acts has his
rivals and unfortunately opponents also. But not because people want
to be opponents, rather because the tasks and relationships force
people to take different points of view. [Dr. Fritz Todt]
V I C T O R Y N O T V E N G E A N C E
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
