--- /dev/null
+#pragma section-numbers off\r
+\r
+This page contains some examples on how to solve common problems with AFS.\r
+\r
+[[TableOfContents]]\r
+\r
+== Making a directory private ==\r
+\r
+If you wish to make a directory within your $HOME completely private so that only you can list, read, and write, do this:\r
+\r
+{{{\r
+mkdir ~/private\r
+fs setacl -clear ~/private <USERNAME> all\r
+}}}\r
+\r
+Note that the {{{-clear}}} option causes any previously set ACLs to be removed. The {{{<USERNAME> all}}} part sets full access to the directory's contents to the specified user. Therefore, if you have a directory in your home directory that you wish to make only accessible to you (such as {{{~/.ssh}}} or {{{~/documents}}}), use:\r
+\r
+{{{fs setacl -clear ~/<DIRECTORY> <USERNAME> all}}}.\r
+\r
+== Serving a website with added privacy ==\r
+\r
+If you use domtool to set up your domain, there is a way to allow {{{system:anyuser}}} only to list the contents of public_html without breaking your website(s). By default ACLs '''R''' and '''L''' are given. Change that in this way: \r
+\r
+{{{\r
+fs setacl ~/public_html system:anyuser l\r
+}}}\r
+\r
+Now, add all permissions for the ''USER.daemon'' principle:\r
+\r
+{{{\r
+fs setacl ~/public_html <USERNAME>.daemon all\r
+}}}\r
+\r
+Be aware that this only works if you use your own domain -- if you use {{{http://deleuze.hcoop.net/~USERNAME}}} to serve your files, then you '''must''' be sure that {{{system:anyuser}}} can read {{{~/public_html}}} and its subdirectories.\r
+\r
+== Setting the rights permissions on your ~/.domtool directory ==\r
+\r
+{{{\r
+fs setacl ~/.domtool domtool read\r
+}}}\r