Changes To AppFS
     6      6   All remote files in AppFS are identified by the SHA1 of their contents so multiple users accessing the same file (content-wise) will share the same locally cached copy.
     7      7   
     8      8   It is similar to the the original 0install implementation, [LazyFS](http://sourceforge.net/projects/zero-install/files/OLD-lazyfs-linux/).  It supports many features required for large scale deployments.  It has the following fancy features:
     9      9   
    10     10      * Write support: Writes are redirected to the users HOME directory
    11     11      * Set-UID root support: Administrators may set conditions on which files are Set-UID root (by default, no files are)
    12     12      * Run-time configuration reloading: All configuration may be reloaded at run-time
    13         -   * PKI support: Package providers can optionally sign index files, which in turn signs all packages and all files in packages
           13  +   * PKI support: Package providers can optionally sign index files, which in turn signs all packages and all files in packages (unsigned indexes are untrusted by default)
    14     14   
    15     15   It should be mounted in `/opt/appfs`.  Once mounted, sub-directories will be automatically made available by attempting to access the hostname of an AppFS server.  For example, `/opt/appfs/core.appfs.rkeene.org` contains:
    16     16   
    17     17   `$ ls -l /opt/appfs/core.appfs.rkeene.org/`<br>
    18     18   `total 0`<br>
    19     19     `dr-xr-xr-x 4 root root 0 Nov 19 04:02 `&nbsp;<font color="blue">`acl`</font>`/`<br>
    20     20   `dr-xr-xr-x 4 root root 0 Nov 19 04:02 `&nbsp;<font color="blue">`appfs`</font>`/`<br>