On Wed, Jan 24, 2001 at 03:04:54AM -0800, Mike Smith wrote:
> I'm not sure that the v3 specification actually cares about telling the
> client "why",
It doesn't, which I think may have been a mistake.
> > For example, a UNIX "open()" call that calls an "access" vnode operation
> > couldn't, if
On Wed, Jan 24, 2001 at 10:28:02AM -0800, Matt Dillon wrote:
> This particular problem, however, is entirely Linux's problem to fix.
Umm, could somebody *PLEASE* show me *ANY* place where I argued that it
wasn't a Linux bug? I can show at least one mail message where I
said it *WAS* a Linux
On Wed, Jan 24, 2001 at 03:17:07AM -0800, Mike Smith wrote:
Content-Description: nfs_vnops.diff
> --- /sys/nfs/nfs_vnops.c Fri Jan 12 14:15:00 2001
> +++ nfs_vnops.c Wed Jan 24 03:01:52 2001
> @@ -387,6 +387,14 @@
>*/
> nfsstats.accesscache_
On Wed, Jan 24, 2001 at 10:42:16AM -0800, Guy Harris wrote:
> 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.
> The "file" command is unable to properly identify EPS binary files. The
> following patch, taken from the magic file included in the Slackware Linux
> distribution, fixes the problem.
Picking up the latest version of "file" from
ftp://ftp.astron.com/pub/file/file-3.32.tar.gz
(or a la
