%general-entities; ]> $Date$ acl The acl package contains utilities to administer Access Control Lists, which are used to define more fine-grained discretionary access rights for files and directories. &lfs75_checked; Package Information Download (HTTP): Download (FTP): Download MD5 sum: &acl-md5sum; Download size: &acl-size; Estimated disk space required: &acl-buildsize; Estimated build time: &acl-time; acl Dependencies Required User Notes: Install acl by running the following commands: sed -i -e 's|/@pkg_name@|&-@pkg_version@|' \ include/builddefs.in && INSTALL_USER=root \ INSTALL_GROUP=root \ ./configure --prefix=/usr --libexecdir=/usr/lib --disable-static && make For meaningful results, the tests need to be carried out on a file system that supports extended attributes. It is also required that Coreutils is re-installed after acl is installed so that the extra acl bit displays correctly on a ls command. Now, as the root user: make install install-dev install-lib && chmod -v 755 /usr/lib/libacl.so && mv -v /usr/lib/libacl.so.* /lib && ln -sfv ../../lib/libacl.so.1 /usr/lib/libacl.so && install -v -m644 doc/*.txt /usr/share/doc/acl-&acl-version; You should now re-install Coreutils and proceed to run the test suite. There are three sets of tests that come with this package. The local partition where the tests are run must be mounted with acl configured as described below. Additionally, the users bin and daemon must be created or modified to have a proper shell and home directory and the group daemon must be a member of the bin group. The kernel must also be configured with the appropriate ACL options (there are nine different options). To run the standard tests run make tests . As root user, run make root-tests. The third set of tests are Network File System (NFS) specific. See the contents of the test files in the test/nfs/ directory for the setup requirements. sed -i ... include/builddefs.in: This command modifies the documentation directory so that it is a versioned directory. --libexecdir=/usr/lib: This switch ensures that libacl.la is installed in the correct directory, and that a spurious libacl.so symlink is not created in /usr/libexec/. There is no configuration to acl itself, but to get any use out of acl, a filesystem needs to support access control lists. One way to achieve this is to add the acl option to an ext3 filesystem in the /etc/fstab file as shown below: # file system mount-point type options dump fsck # order /dev/sda1 / ext3 defaults,acl,user_xattr 0 2 Installed Programs Installed Library Installed Directories chacl, getfacl, and setfacl libacl.{so,a} /usr/{include/acl,share/doc/acl-&acl-version;} Short Descriptions chacl changes the access control list of a file or directory. chacl getfacl gets file access control lists. getfacl setfacl sets file access control lists. setfacl libacl.{so,a} contains the acl API functions. libacl.{so,a}