Subject: proposed text for issue07

From: Mike Eisler <[email-masked]>
Date: Thu, 29 Aug 2002 12:55:21 -0700

The original post for this issue starts here 

    Regarding,

       ACCESS4_DELETE  Delete an existing directory entry (no meaning for
    		       non-directory objects).
    
    	    [...]

	 Many implementations do not directly support the
	 ACCESS4_DELETE permission.  Operating systems like
	 UNIX will ignore the ACCESS4_DELETE bit if set
	 on an access request on a non-directory object.
	 In these systems, delete permission on a file
	 is determined by the access permissions on the
	 directory in which the file resides, instead
	 of being determined by the permissions of the
	 file itself.

    The paragraph fragment above seems to imply some
    implementations do directly support ACCESS4_DELETE
    on non-directories. If so, this contradicts what was
    first written about ACCESS4_DELETE.

Resolve the conflicting text. 

----------

Looking at the NFSv3 specification, it says for ACCESS3_DELETE:

         ACCESS3_DELETE
            Delete an existing directory entry.

I.e. no "(no meaning for non-directory objects)."
fragment that the v4 specification has. I think NFSv3 has this one
right.

Proposed text:

CHANGE:

   ACCESS4_DELETE  Delete an existing directory entry (no meaning for
                   non-directory objects).

TO:

   ACCESS4_DELETE  Delete an existing directory entry.