Differences between current version and predecessor to the previous major change of ACL.
Other diffs: Previous Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 5 | Last edited on Wednesday, June 2, 2004 12:59:32 pm | by JohnMcPherson | |
| Older page: | version 2 | Last edited on Wednesday, June 2, 2004 8:54:06 am | by JohnMcPherson | Revert |
@@ -6,16 +6,21 @@
user=JohnMcPherson,rx
group=WLUG,x
other=none
-would give PerryLorier,MattBrown read/write access to some executable, JohnMcPherson gets to read the executable, and everyone in the group WLUG would be able to read
it. Linux 2.6 supports ACL's
on some filesystems (such as ext2
)
+would give PerryLorier,MattBrown read/write access to some executable, JohnMcPherson gets to read the executable, and everyone in the group WLUG would be able to execute
it. Linux 2.6 supports ACLs
on some filesystems (such as [Ext2]
).
For example, [Solaris] allows you to do this. You can use the commands
''setfacl'' and ''getfacl'' to see file ACLs.
The way this is implemented in Solaris, the presence of file ACLs is
specified by a __+__ character next to the "normal" access indicators:
$ ls -ld Projects
drwxr-xr-x__+__ 3 user group 4096 2004-01-07 22:29 Projects
+
+[FreeBSD]s ACLs work much in the same way as [Solaris]. FreeBSD 5 with UFS2 supports ACLs by default (they can be enabled by recompilation for UFS1 and FreeBSD 4), but you have to mount your filesystem with
+ mount -o acl
+
+for the ''setfacl'' tool to work.
You can then use setfacl to give write access to multiple users and groups (for example), rather than having to create a new group and
adding all the requisite users to that group.
