| 1 |
|
| 2 |
Requirements |
| 3 |
============ |
| 4 |
|
| 5 |
- autofs 5.0.0 requires protocol version 5.00 of the autofs4 kernel |
| 6 |
module (see "Applying the kernel patch" below). |
| 7 |
|
| 8 |
- The LDAP, SASL, and the libxml2 libraries may also be required if |
| 9 |
the LDAP configure options are selected (see "Configure options for |
| 10 |
autofs" below). |
| 11 |
|
| 12 |
How to build and install |
| 13 |
======================== |
| 14 |
|
| 15 |
To configure, compile, and install the package directly from the |
| 16 |
tar distribution, follow these steps. |
| 17 |
|
| 18 |
1. Make sure you have the latest version of the package available |
| 19 |
from http://www.kernel.org/pub/linux/daemons/autofs/v4. |
| 20 |
|
| 21 |
2. Type `./configure' to configure the package. You may want to add |
| 22 |
selected configure options. See "Configure options for autofs" |
| 23 |
below. |
| 24 |
|
| 25 |
3. Build the package by typing `make' |
| 26 |
|
| 27 |
4. Install the package by typing `make install'. |
| 28 |
|
| 29 |
To build an `rpm' from the tar distribution use: |
| 30 |
|
| 31 |
rpmbuild -tb autofs-5.0.0_beta6.tar.gz |
| 32 |
|
| 33 |
and install the resulting rpm package. |
| 34 |
|
| 35 |
Configure options for autofs |
| 36 |
============================ |
| 37 |
|
| 38 |
There are several configure options available to add functionality. |
| 39 |
|
| 40 |
--prefix=<root_prefix> |
| 41 |
autofs usually installs in /usr, with the daemon in /usr/sbin, |
| 42 |
the man pages in /usr/man, and the modules in /usr/lib/autofs. |
| 43 |
If you wish to install to a different location use this option. |
| 44 |
|
| 45 |
--with-path=PATH |
| 46 |
Allows the specification of the path to search for utility |
| 47 |
binaries used by autofs during the `configure' process. If |
| 48 |
any of your binaries such as `mount', `mount.cifs' etc. live |
| 49 |
in locations other than /usr/bin:/bin:/usr/sbin:/sbin you |
| 50 |
will need to use this option. |
| 51 |
|
| 52 |
--disable-ext-env |
| 53 |
This option disables the ability to the external environment |
| 54 |
to set an external environment variable for substitution. |
| 55 |
|
| 56 |
--disable-mount-locking |
| 57 |
This option disables mount locking which is to prevent corruption |
| 58 |
in /etc/mtab due to multiple concurrent autofs mount commands. |
| 59 |
|
| 60 |
--enable-force-shutdown |
| 61 |
This option enables the use of the USR1 signal to force an |
| 62 |
unconditional unlink umount of all mounts at shutdown. |
| 63 |
|
| 64 |
--enable-ignore-busy |
| 65 |
This option enables the automount to exit ignoring any busy |
| 66 |
mounts upon receiving a TERM signal. automount attempts to |
| 67 |
recover upon startup. |
| 68 |
|
| 69 |
--with-confdir=DIR |
| 70 |
This option allows the specification of the directory that contains |
| 71 |
the autofs configuration file `autofs'. If not given the directories |
| 72 |
`/etc/sysconfig', `/etc/default' and `/etc/conf.d' and checked for |
| 73 |
existence and the first one found is used. |
| 74 |
|
| 75 |
--with-mapdir=PATH |
| 76 |
This option allows the specification of the directory that contains |
| 77 |
autofs mount maps. The directories `/etc/autofs' and `/etc' are |
| 78 |
checked for existence and first one found is used. |
| 79 |
|
| 80 |
--with-hesiod=DIR |
| 81 |
Use this option to enable Hesiod support if your Hesiod library |
| 82 |
isn't installed in /usr/lib with the include files in /usr/include. |
| 83 |
|
| 84 |
--with-openldap=DIR |
| 85 |
Use this To enable LDAP support if your OpenLDAP library isn't |
| 86 |
installed in /usr/lib with the include files in /usr/include. |
| 87 |
|
| 88 |
--with-sasl=DIR |
| 89 |
Use this to enable TLS encrypted connections and LDAP |
| 90 |
authentication using the SASL library. DIR only needs to be |
| 91 |
given if your LDAP and SASL library and include files are |
| 92 |
installed in other than /usr/lib and /usr/include. See |
| 93 |
auto.master(5) for more information about LDAP configuration. |
| 94 |
|
| 95 |
Applying The Kernel Patch |
| 96 |
========================= |
| 97 |
|
| 98 |
Patches that can be applied to the kernel are located in the |
| 99 |
`patches' directory. If you have installed autofs from an rpm |
| 100 |
then they can be found in the packages' doc directory after |
| 101 |
install. They consist of a kernel patch for each kernel from |
| 102 |
2.6.9 thru 2.6.16 (the patches are in the 2.6.17-rc series so |
| 103 |
patching a 2.6.17 or above kernel shouldn't be needed). If |
| 104 |
you need a patch for an older 2.6 kernel then post to the |
| 105 |
autofs mailing list and ask for one to be done. |
| 106 |
|
| 107 |
To apply one of these patches: |
| 108 |
|
| 109 |
1) change to the root of your kernel source tree. |
| 110 |
2) patch the kernel |
| 111 |
3) make the kernel |
| 112 |
4) Install the kernel as normal. |
| 113 |
|
| 114 |
If you use a packaged kernel then you need to check to see if |
| 115 |
the v5 update patch will apply and if it does apply add the |
| 116 |
update patch and build your packaged kernel. |
| 117 |
|
| 118 |
For example, Fedora Core 4 kernel package 2.6.11-1.369_FC4 |
| 119 |
would use the 2.6.12 patch because it applies the 2.6.12 release |
| 120 |
candidate revision 6 patch. But the autofs patch doesn't apply |
| 121 |
because the rpm also applies a patch somewhere that changes one |
| 122 |
area the patch also changes but this change is not present |
| 123 |
in the 2.6.12 release kernel. |
| 124 |
|
| 125 |
On the other hand, Fedora Core 3 kernel 2.6.12-1.1381_FC3 |
| 126 |
uses the 2.6.12 patch and it applies cleanly because the kernel |
| 127 |
doesn't apply a 2.6.13 release candidate patch and there are no |
| 128 |
additional patches that clash with the autofs update patch. To |
| 129 |
build this kernel with an update patch modify the kernel-2.6.spec |
| 130 |
to apply the update patch after all other patches (see example |
| 131 |
change below), copy the autofs4-2.6.12-v5-update to the SOURCES |
| 132 |
directory of your RPM build tree and us use |
| 133 |
`rpmbuild -bb --target=i686 kernel-2.6.spec' in the SPEC directory |
| 134 |
of the build tree and install the resulting RPMs. |
| 135 |
|
| 136 |
Example of how to add the update patch: |
| 137 |
|
| 138 |
--- kernel-2.6.spec.orig 2006-05-01 10:14:27.000000000 +0800 |
| 139 |
+++ kernel-2.6.spec 2006-05-01 10:16:21.000000000 +0800 |
| 140 |
@@ -358,6 +358,8 @@ |
| 141 |
Patch10000: linux-2.6.0-compile.patch |
| 142 |
Patch10001: linux-2.6-compile-fixes.patch |
| 143 |
|
| 144 |
+Patch20000: autofs4-2.6.12-v5-update.patch |
| 145 |
+ |
| 146 |
# END OF PATCH DEFINITIONS |
| 147 |
|
| 148 |
BuildRoot: %{_tmppath}/kernel-%{KVERREL}-root |
| 149 |
@@ -739,6 +741,7 @@ |
| 150 |
%patch10000 -p1 |
| 151 |
%patch10001 -p1 |
| 152 |
|
| 153 |
+%patch20000 -p1 |
| 154 |
|
| 155 |
# END OF PATCH APPLICATIONS |
| 156 |
|
| 157 |
Some Fedora Core kernels have autofs4 bug fix patches, such as |
| 158 |
2.6.16-1.2096_FC5. The update patch supersedes all previous patches |
| 159 |
so any additional autofs4 patches should be removed and the update |
| 160 |
patch added. For example 2.6.16-1.2096_FC5 needs this change: |
| 161 |
|
| 162 |
--- kernel-2.6.spec.orig 2006-06-18 14:56:27.000000000 +0800 |
| 163 |
+++ kernel-2.6.spec 2006-06-18 14:56:52.000000000 +0800 |
| 164 |
@@ -359,7 +359,7 @@ |
| 165 |
Patch1630: linux-2.6-radeon-backlight.patch |
| 166 |
Patch1640: linux-2.6-ide-tune-locking.patch |
| 167 |
Patch1641: linux-2.6-ide-cd-shutup.patch |
| 168 |
-Patch1650: linux-2.6-autofs-pathlookup.patch |
| 169 |
+#Patch1650: linux-2.6-autofs-pathlookup.patch |
| 170 |
Patch1660: linux-2.6-valid-ether-addr.patch |
| 171 |
Patch1670: linux-2.6-softcursor-persistent-alloc.patch |
| 172 |
Patch1680: linux-2.6-pwc-powerup-by-default.patch |
| 173 |
@@ -983,7 +983,7 @@ |
| 174 |
# Silence noisy CD drive spew |
| 175 |
%patch1641 -p1 |
| 176 |
# autofs4 looks up wrong path element when ghosting is enabled |
| 177 |
-%patch1650 -p1 |
| 178 |
+#%patch1650 -p1 |
| 179 |
# |
| 180 |
%patch1660 -p1 |
| 181 |
# Use persistent allocation in softcursor |