From a2eb2e366234455b59a57bc5760c2ee62815df1f Mon Sep 17 00:00:00 2001 From: rwatson Date: Sat, 19 Oct 2002 16:09:16 +0000 Subject: [PATCH] Clarify that the UFS1 extended attribute configuration steps do not apply to UFS2 file systems. Submitted by: jedgar Obtained from: TrustedBSD Project --- sys/ufs/ufs/README.acls | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/sys/ufs/ufs/README.acls b/sys/ufs/ufs/README.acls index d921bd7fdf0e..28a9d4f59d87 100644 --- a/sys/ufs/ufs/README.acls +++ b/sys/ufs/ufs/README.acls @@ -50,7 +50,7 @@ system. For reliability and performance reasons, the use of ACLs on UFS1 is discouraged; UFS2 extended attributes provide a more reliable storage mechanism for ACLs. -Currently, support for ACLs on UFS requires the use of UFS EAs, which may +Currently, support for ACLs on UFS1 requires the use of UFS1 EAs, which may be enabled by adding: options UFS_EXTATTR @@ -65,7 +65,7 @@ required extended attributes with the filesystem mount operation. To enable ACLs, two extended attributes must be available in the EXTATTR_NAMESPACE_SYSTEM namespace: "posix1e.acl_access", which holds the access ACL, and "posix1e.acl_default" which holds the default ACL -for directories. If you're using UFS Extended Attributes, the following +for directories. If you're using UFS1 Extended Attributes, the following commands may be used to create the necessary EA backing files for ACLs in the filesystem root of each filesystem. In these examples, the root filesystem is used; see README.extattr for more details.