-For generic installation instructions see the file INSTALL in the main
-source directory.
+Quickly:
+$> ./autogen.sh
+$> ./configure [options]
+$> make
+$> make install
-Netatalk supports some additional option to the ./configure script.
-These are:
+
+1. ./autogen.sh (Not necessary for a release tarball.)
+This shell script runs libtoolize, aclocal, autoheader, automake and
+autoconf. This sets up all the conditions for the next step. You may
+or may not have to do this. If you downloaded a release tarball, or if
+your download contains a ./configure file then this has already been
+run for you.
+
+2. ./configure
+This step reads the options to the ./configure program and checks your
+system against the requirements of those options. It generally fails
+if your system doesn't meet the requirements.
+
+Netatalk options to the ./configure script: Use ./configure --help for
+a complete list.
--disable-admin-group: disable admin group (default on),
---disable-ddp: disable DDP support,
+--disable-ddp: disable DDP support (AppleTalk),
---enable-dropkludge: enable the experimental dropbox fix (INSECURE!)
+--enable-debug: enable debugging messages in syslog,
---with-shadow: enable shadow password support,
+--enable-dropkludge: enable the experimental dropbox fix
+ (INSECURE!),
+
+--enable-cnid-db: use persistent cnid database per volume
+ (EXPERIMENTAL),
+
+--with-db3=PATH: specify path to Berkeley DB3 installation,
+
+--with-did=[scheme]: set DID scheme (last,mtab),
+
+--with-msg-dir=path: path to message files [default=/etc/msg],
+
+--enable-srvloc: Turn on Server Location Protocol support (EXPERIMENTAL),
--with-pam: enable pluggable authentication modules support,
- PAM provides a flexible mechanism for authenticating
- users. PAM was invented by SUN Microsystems.
- Author: Andrew Morgan <morgan@linux.kernel.org>
+ PAM provides a flexible mechanism for authenticating
+ users. PAM was invented by SUN Microsystems.
+
+ Linux-PAM is a suite of shared libraries that enable the local
+ system administrator to choose how applications authenticate users.
+ You can get the Linux PAM documentation and sources from
+ http://www.kernel.org/pub/linux/libs/pam/
+
+--with-shadow: enable shadow password support,
- Linux-PAM is a suite of shared libraries that enable the local
- system administrator to choose how applications authenticate users.
- You can get the Linux PAM documentation and sources from
- http://www.kernel.org/pub/linux/libs/pam/
+--disable-shell-check: disable checking for a valid shell,
+--with-flock-locks: enable flock locks support,
--with-tcp-wrappers: enable TCP wrappers support.
- Wietse Venema's network logger, also known as TCPD or
- LOG_TCP. These programs log the client host name of incoming
- telnet, ftp, rsh, rlogin, finger etc. requests. Security
- options are: access control per host, domain and/or service;
- detection of host name spoofing or host address spoofing;
- booby traps to implement an early-warning system. TCP
- Wrappers can be gotten at
- ftp://ftp.porcupine.org/pub/security/
+ Wietse Venema's network logger, also known as TCPD or
+ LOG_TCP. These programs log the client host name of incoming
+ telnet, ftp, rsh, rlogin, finger etc. requests. Security
+ options are: access control per host, domain and/or service;
+ detection of host name spoofing or host address spoofing;
+ booby traps to implement an early-warning system. TCP
+ Wrappers can be gotten at
+ ftp://ftp.porcupine.org/pub/security/
--with-ssl-dirs=[PATH]: specify path to OpenSSL installation.
- NOTE: This is dependent on the same directory layout as the
- source distribution of Openssl. That is: ./include/ and
- ./lib/ to be on the same level. Many .rpm formats do not
- have their files laid out in this format.
- The OpenSSL Project is a collaborative effort to develop a
- robust, commercial-grade, full-featured, and Open Source
- toolkit implementing the Secure Sockets Layer (SSL v2/v3)
- and Transport Layer Security (TLS v1) protocols as well as a
- full-strength general purpose cryptography library.
- This is required to enable DHX login support.
- Get everything at http://www.openssl.org/
+ NOTE: This is dependent on the same directory layout as the
+ source distribution of Openssl. That is: ./include/ and
+ ./lib/ to be on the same level. Many .rpm formats do not
+ have their files laid out in this format.
+ The OpenSSL Project is a collaborative effort to develop a
+ robust, commercial-grade, full-featured, and Open Source
+ toolkit implementing the Secure Sockets Layer (SSL v2/v3)
+ and Transport Layer Security (TLS v1) protocols as well as a
+ full-strength general purpose cryptography library.
+ This is required to enable DHX login support.
+ Get everything at http://www.openssl.org/
--with-lastdid: Recreate version 37b behaviour where
- directory id's are incrementally calculated versus the new
- hash method. Unfortunately for machines that have a lot of
- devices, and/or a lot of inodes the hash can fail with
- multiple directories resolving to the same DID.
+ directory id's are incrementally calculated versus the new
+ hash method. Unfortunately for machines that have a lot of
+ devices, and/or a lot of inodes the hash can fail with
+ multiple directories resolving to the same DID.
+
+--with-uams-path=path: path to UAMs [default=PKGCONF/uams]
+
+--enable-fhs: use Filesystem Hierarchy Standard (FHS) compatibility
+
+--with-ssl-dir=PATH: specify path to openssl installation (must contain
+ lib and include dirs)
+
+--enable-pgp-uam: enable build of PGP UAM module
+
+--enable-krb4-uam: enable build of Kerberos v4 UAM module
+
+--enable-overwrite: Overwrite configuration files in PKGCONFDIR
+
+
+3. ./make
+
+Compile all of the programs
+
+4. ./make install
+Install the programs in the places specified by the ./configure process.