89 model.
90
91 o NFSv4 ACLs allow for both ALLOW and DENY entries.
92
93 o NFSv4 ACLs provide a rich set of inheritance semantics.
94 POSIX ACLs also have inheritance, but with the NFSv4 model
95 you can control the following inheritance features:
96
97 o Whether inheritance cascades to both files and
98 directories or only to files or directories.
99
100 o In the case of directories, you can indicate whether
101 inheritance is applied to the directory itself, to just
102 one level of subdirectories, or cascades to all
103 subdirectories of the directory.
104
105 o NFSv4 ACLs provide a mechanism for hooking into a system's
106 audit trail. Currently, Solaris does not support this
107 mechanism.
108
109 o NFSv4 ACLs enable adminstrators to specify the order in
110 which ACL entries are checked. With POSIX-draft ACLs the
111 file system reorders ACL entries into a well defined, strict
112 access, checking order.
113
114
115 POSIX-draft ACL semantics can be achieved with NFSv4 ACLs. However,
116 only some NFSv4 ACLs can be translated to equivalent POSIX-draft ACLs.
117
118
119 Permissions can be specified in three different chmod ACL formats:
120 verbose, compact, or positional. The verbose format uses words to
121 indicate that the permissions are separated with a forward slash (/)
122 character. Compact format uses the permission letters and positional
123 format uses the permission letters or the hypen (-) to identify no
124 permissions.
125
126
127 The permissions for verbose mode and their abbreviated form in
128 parentheses for compact and positional mode are described as follows:
129
130 read_data (r)
131 Permission to read the data of the file
132
133
134 list_directory (r)
135 Permission to list the contents of a directory.
136
137
138 write_data (w)
139 Permission to modify a file's data anywhere in
140 the file's offset range. This includes the
141 ability to grow the file or write to any
142 arbitrary offset.
143
|
89 model.
90
91 o NFSv4 ACLs allow for both ALLOW and DENY entries.
92
93 o NFSv4 ACLs provide a rich set of inheritance semantics.
94 POSIX ACLs also have inheritance, but with the NFSv4 model
95 you can control the following inheritance features:
96
97 o Whether inheritance cascades to both files and
98 directories or only to files or directories.
99
100 o In the case of directories, you can indicate whether
101 inheritance is applied to the directory itself, to just
102 one level of subdirectories, or cascades to all
103 subdirectories of the directory.
104
105 o NFSv4 ACLs provide a mechanism for hooking into a system's
106 audit trail. Currently, Solaris does not support this
107 mechanism.
108
109 o NFSv4 ACLs enable administrators to specify the order in
110 which ACL entries are checked. With POSIX-draft ACLs the
111 file system reorders ACL entries into a well defined, strict
112 access, checking order.
113
114
115 POSIX-draft ACL semantics can be achieved with NFSv4 ACLs. However,
116 only some NFSv4 ACLs can be translated to equivalent POSIX-draft ACLs.
117
118
119 Permissions can be specified in three different chmod ACL formats:
120 verbose, compact, or positional. The verbose format uses words to
121 indicate that the permissions are separated with a forward slash (/)
122 character. Compact format uses the permission letters and positional
123 format uses the permission letters or the hyphen (-) to identify no
124 permissions.
125
126
127 The permissions for verbose mode and their abbreviated form in
128 parentheses for compact and positional mode are described as follows:
129
130 read_data (r)
131 Permission to read the data of the file
132
133
134 list_directory (r)
135 Permission to list the contents of a directory.
136
137
138 write_data (w)
139 Permission to modify a file's data anywhere in
140 the file's offset range. This includes the
141 ability to grow the file or write to any
142 arbitrary offset.
143
|