ACL: Difference between revisions

Revision as of 11:18, 16 March 2017

Using ACL to make an actually useable shared folder

Sadly the built in UNIX way of doing permissions, with it's notions of users, groups, and "others" is in practice quite difficult to use to make "shared folders". ACL (for access control lists) is an extension to these mechanisms that gives more flexibility. The setfacl command is the thing that sets the options.

So, the command to Allow anyone in the users group to write files to path/to/some/folder

 setfacl -Rm g:users:rwX /path/to/some/folder/
 setfacl -d -Rm g:users:rwX /path/to/some/folder/

@@ Line 2: / Line 2: @@
 == Using ACL to make an actually useable shared folder ==
-Sadly the built in UNIX way of doing permissions, with it's notions of users, groups, and "others" is in practice quite difficult to use to make "shared folders". [http://www.linuxcommand.org/man_pages/setfacl1.html FACL] (for file access control lists) is an extension to these mechanisms that gives more flexibility.
+Sadly the built in UNIX way of doing permissions, with it's notions of users, groups, and "others" is in practice quite difficult to use to make "shared folders". [http://bencane.com/2012/05/27/acl-using-access-control-lists-on-linux/ ACL] (for access control lists) is an extension to these mechanisms that gives more flexibility. The [http://www.linuxcommand.org/man_pages/setfacl1.html setfacl] command is the thing that sets the options.
 So, the command to Allow anyone in the users group to write files to path/to/some/folder