Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!usc!cs.utexas.edu!uunet!murtoa.cs.mu.oz.au!munnari.oz.au!otc!softway!chris
From: chris@softway.oz (Chris Maltby)
Newsgroups: comp.unix.wizards
Subject: Re: Unexpected NFS Effects
Message-ID: <1703@softway.oz>
Date: 19 Jun 89 02:05:55 GMT
References: <403@fang.dsto.oz> <12025@bloom-beacon.MIT.EDU>
Organization: Softway Pty Ltd, Sydney, Australia
Lines: 14

Jonathan I. Kamens writes:
: Now, NFS can draw no distinction between a root user making a read
: request and a kernel [...] making read requests, and there is no
: difference in NFS between a "read for user viewing" and "read for
: execution" request.

So that's how it is, I'm sure. The question now is "Why?". I can't think
of any reason why you couldn't pass a "read for execution" request distinct
from a "read as data" request. I guess someone crocked the design... (:-)
-- 
Chris Maltby - Softway Pty Ltd	(chris@softway.sw.oz)

PHONE:	+61-2-698-2322		UUCP:		uunet!softway.sw.oz.au!chris
FAX:	+61-2-699-9174		INTERNET:	chris@softway.sw.oz.au