4
DAVFS2 1.3.2 INSTALLATION
5
=========================
7
1 UPDATING FROM PREVIOUS VERSION
10
2.2 INSTALLATION FROM CVS SOURCES
11
2.3 INSTALLATION FROM SOURCE PACKAGE
15
1 UPDATING FROM PREVIOUS VERSION
16
================================
18
'make install' copies new versions of davfs2.conf and secrets
19
into /usr/local/etc/davfs2 or /etc/davfs2 and creates a backup of the
20
existing files. You will have to merge your changes from the backup
23
When a user invokes the new version of mount.davfs thefirst time, it
24
will only copy new versions of davfs2.conf and secrets into ~/.davfs2,
25
if this files do not exist. The user should rename this files before
26
invoking mount.davfs. After the new configuration files have been
27
installed the user may merge the changes form the old files into
34
In davfs2 1.1.0 the organization of the permanent cache has changed
35
compared to the 1.0.x releases and the cache needs to be rebuild. Files
36
in the backup directory will be lost. So before installing the new version,
37
you should start your old version of mount.davfs a last time and save all
38
the files from the backup directory you may need some day.
47
davfs2 uses the neon libraries for communication with the server.
48
libneon (2.5, 2.6, 2.7 or 2.8) must be installed. Your distribution will most
49
likely provide a package.
50
You will also need the neon header files. Distributions usually provide
51
development packages for this.
52
If your distribution don't come with libneon or it does not support TLS and
53
large files, you may build your own neon library. You can get it from
54
http://www.webdav.org/neon/
56
Your kernel must include either the coda file system or the fuse file system
57
or both. They may be loadable modules. Almost all Linux 2.4 and 2.6 kernels
58
support at least one of them.
61
2.2 INSTALLATION FROM CVS SOURCES
62
---------------------------------
64
To build davfs2 from the CVS sources you need recent versions of the some
67
- GNU Autoconf 2.61 or newer
68
- GNU Automake 1.10 or newer
69
- GNU gettext-tools 0.16.1 or newer
72
Change into the top level source directory and run
74
This will add some necessary files, create the configure script and the
75
Makefile.in's, and build the translated man pages from the po-files.
77
Proceed with Installation from Source Package.
80
2.3 INSTALLATION FROM SOURCE PACKAGE
81
------------------------------------
83
From within the top level source directory:
85
- Run the configure script.
86
$ ./configure [options]
87
This will test your system and finally create the appropriate Makefiles.
88
You may add some options or set some variables, but hopefully will not
91
Options and variables:
92
----------------------
95
Defines the directory where davfs2 will be installed. It defaults to
96
'/usr/local'. If your sources came with your distribution it may
99
--with-neon=<directory>
100
Directory where to find the neon library and the neon headers.
101
Default is to first try /usr/local and then /usr. If you just have
102
neon liebraries in /usr/lib and headers in /usr/include, you don't
106
Disable the support for national lanuages.
109
A list of two-letter language codes. This will select which of the
110
available translations of messages and documentation will be installed.
111
ll must be in lower case.
114
A system user without shell. mount.davfs will run with this id when
115
invoked by root. Default dav_user is "davfs2".
118
A system group. mount.davfs will be member of this group. Normal users
119
must be member of this group in order to mount. Default dav_group is
122
./configure --help will show all available options.
126
This will compile the program.
128
- Gain root permissions and run make install.
130
This will copy all the files in the appropriate directory.
131
Note: 'mount.davfs' will be setuid!
133
- Create the system user 'davfs2' and group 'davfs2' if they not yet exist.
134
The system user should not have a shell. Proposed home directory is
137
- Get rid of the root permissions.
143
To uninstall davfs2 the sources have to be configured just the same way
144
they were configured for installation.
146
From within the top level source directory run with root permissions
148
This will remove all the installed files.
150
Note: The directories will not be removed.
151
Files and directories created by mount.davfs at run-time will *not* be
153
This are: pid-files (in /var/run/mount.davfs), cache files and
154
directories (in /var/cache/davfs2) and all the files in the users
155
home directories in .davfs2.
156
This files have to be removed manually.