From owner-freebsd-doc  Sun May  6 16:13:11 2001
Delivered-To: freebsd-doc@freebsd.org
Received: from smtp1.interramp.com (smtp1.interramp.com [38.8.45.2])
	by hub.freebsd.org (Postfix) with ESMTP id C91E337B422
	for <doc@freebsd.org>; Sun,  6 May 2001 16:13:07 -0700 (PDT)
	(envelope-from horikawa@psinet.com)
Received: from [38.26.194.34] (helo=localhost)
	by smtp1.interramp.com with esmtp (Exim 1.90 #1)
	for doc@FreeBSD.org
	id 14wXi5-0002eG-00; Sun, 6 May 2001 19:13:05 -0400
To: doc@FreeBSD.org
Subject: Questions/comments about description in VOP_XXX(9)
X-Mailer: Mew version 1.94.1 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <20010506191347G.horikawa@psinet.com>
Date: Sun, 06 May 2001 19:13:47 -0400
From: Kazuo Horikawa <horikawa@psinet.com>
X-Dispatcher: imput version 20000228(IM140)
Lines: 64
Sender: owner-freebsd-doc@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Hi,

During checking section 9 manpages translated into non-English
(Japanese), I had a couple of questions/comments about descriptions in
VOP_XXX(9).

I appreciate it, if someone could see whether my understanding is
correct or not.

Thanks in advance!

[1. what is `of possible' phrase]
  I found `of possible' phrase in most of VOP_XXX(9).
  I guess this phrase has similar meaning as `if possible'.  Is my
  understanding correct?

  For example, I could find following paragraph in VOP_SETACL(9):

     The cred pointer may be NULL to indicate that access control checks are
     not to be performed, of possible.  This cred setting might be used to al-
     low the kernel to authorize extended attribute changes that the active
     process might not be permitted to make.


[2. VOP_SETACL(9) says about extended attributed, instead of ACL]
  I am afraid that paragraph above contains typo, since VOP_SETACL(9)
  should deal with `ACL' instead of `named extended attribute.'
  If my understanding correct, how about applying following patch
  for VOP_SETACL(9)?

--- VOP_SETACL.9.orig   Sun May  6 18:11:47 2001
+++ VOP_SETACL.9        Sun May  6 18:21:47 2001
@@ -66,8 +66,8 @@
 pointer may be
 .Dv NULL
 to indicate that access control checks are not to be performed, of possible.
-This cred setting might be used to allow the kernel to authorize extended
-attribute changes that the active process might not be permitted to make.
+This cred setting might be used to allow the kernel to authorize ACL
+changes that the active process might not be permitted to make.
 .Pp
 The vnode ACL interface defines the syntax, and not semantics, of file and
 directory ACL interfaces.  More information about ACL management in kernel


[3. EOPNOTSUPP of VOP_SETEXTATTR(9) says about VOP_GETEXTATTR(9)]
  In VOP_SETEXTATTR(9), I think VOP_GETEXTATTR() should be replaced
  with VOP_SETEXTATTR().
  If my understanding correct, how about following patch for
  VOP_SETEXTATTR(9)?

--- VOP_SETEXTATTR.9.orig       Sun May  6 18:37:50 2001
+++ VOP_SETEXTATTR.9    Sun May  6 18:38:04 2001
@@ -103,7 +103,7 @@
 The name or uio argument is invalid
 .It Bq Er EOPNOTSUPP
 The file system does not support
-.Fn VOP_GETEXTATTR
+.Fn VOP_SETEXTATTR
 .It Bq Er ENOSPC
 The file system is out of space
 .It Bq Er EROFS
--
Kazuo Horikawa

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-doc" in the body of the message