140 .RS +4
 141 .TP
 142 .ie t \(bu
 143 .el o
 144 In the case of directories, you can indicate whether inheritance is applied to
 145 the directory itself, to just one level of subdirectories, or cascades to all
 146 subdirectories of the directory.
 147 .RE
 148 .RE
 149 .RS +4
 150 .TP
 151 .ie t \(bu
 152 .el o
 153 NFSv4 ACLs provide a mechanism for hooking into a system's audit trail.
 154 Currently, Solaris does not support this mechanism.
 155 .RE
 156 .RS +4
 157 .TP
 158 .ie t \(bu
 159 .el o
 160 NFSv4 ACLs enable adminstrators to specify the order in which ACL entries are
 161 checked. With POSIX-draft ACLs the file system reorders ACL entries into a well
 162 defined, strict access, checking order.
 163 .RE
 164 .sp
 165 .LP
 166 POSIX-draft ACL semantics can be achieved with NFSv4 ACLs. However, only some
 167 NFSv4 ACLs can be translated to equivalent POSIX-draft ACLs.
 168 .sp
 169 .LP
 170 Permissions can be specified in three different \fBchmod\fR ACL formats:
 171 verbose, compact, or positional. The verbose format uses words to indicate that
 172 the permissions are separated with a forward slash (\fB/\fR) character. Compact
 173 format uses the permission letters and positional format uses the permission
 174 letters or the hypen (\fB-\fR) to identify no permissions.
 175 .sp
 176 .LP
 177 The permissions for verbose mode and their abbreviated form in parentheses for
 178 compact and positional mode are described as follows:
 179 .sp
 180 .ne 2
 181 .na
 182 \fBread_data (\fBr\fR)\fR
 183 .ad
 184 .RS 24n
 185 Permission to read the data of the file
 186 .RE
 187 
 188 .sp
 189 .ne 2
 190 .na
 191 \fBlist_directory (\fBr\fR)\fR
 192 .ad
 193 .RS 24n
 194 Permission to list the contents of a directory.

 140 .RS +4
 141 .TP
 142 .ie t \(bu
 143 .el o
 144 In the case of directories, you can indicate whether inheritance is applied to
 145 the directory itself, to just one level of subdirectories, or cascades to all
 146 subdirectories of the directory.
 147 .RE
 148 .RE
 149 .RS +4
 150 .TP
 151 .ie t \(bu
 152 .el o
 153 NFSv4 ACLs provide a mechanism for hooking into a system's audit trail.
 154 Currently, Solaris does not support this mechanism.
 155 .RE
 156 .RS +4
 157 .TP
 158 .ie t \(bu
 159 .el o
 160 NFSv4 ACLs enable administrators to specify the order in which ACL entries are
 161 checked. With POSIX-draft ACLs the file system reorders ACL entries into a well
 162 defined, strict access, checking order.
 163 .RE
 164 .sp
 165 .LP
 166 POSIX-draft ACL semantics can be achieved with NFSv4 ACLs. However, only some
 167 NFSv4 ACLs can be translated to equivalent POSIX-draft ACLs.
 168 .sp
 169 .LP
 170 Permissions can be specified in three different \fBchmod\fR ACL formats:
 171 verbose, compact, or positional. The verbose format uses words to indicate that
 172 the permissions are separated with a forward slash (\fB/\fR) character. Compact
 173 format uses the permission letters and positional format uses the permission
 174 letters or the hyphen (\fB-\fR) to identify no permissions.
 175 .sp
 176 .LP
 177 The permissions for verbose mode and their abbreviated form in parentheses for
 178 compact and positional mode are described as follows:
 179 .sp
 180 .ne 2
 181 .na
 182 \fBread_data (\fBr\fR)\fR
 183 .ad
 184 .RS 24n
 185 Permission to read the data of the file
 186 .RE
 187 
 188 .sp
 189 .ne 2
 190 .na
 191 \fBlist_directory (\fBr\fR)\fR
 192 .ad
 193 .RS 24n
 194 Permission to list the contents of a directory.