i386_linux22, i386_linux24, i386_linux26
i386_umlinux22, i386_umlinux24
i386_obsd31, i386_obsd32, i386_obsd33, i386_obsd34, i386_obsd35,
- i386_obsd36
+ i386_obsd36, i386_obsd37, i386_obsd38
rs_aix42
sgi_65 (file server not tested)
sun4_413 (No client support, no fileserver support, db servers only)
- sun4x_56, sun4x_57, sun4x_58, sun4x_59 (logging UFS not supported
+ sun4x_56, sun4x_57, sun4x_58, sun4x_59, sun4x_510,
+ sunx86_57, sunx86_58, sunx86_59, sunx86_510 (logging UFS not supported
for mixed-use partitions containing client cache)
ppc_darwin_70
ppc_linux22, ppc_linux24
ia64_linux24, ia64_linux26
sparc_linux22, sparc_linux24
sparc64_linux22, sparc64_linux24
- hp_ux110 (See notes below for information on getting missing header)
+ hp_ux11i, hp_ux110 (See notes below for information on getting
+ missing header)
hp_ux102 (Client port possible, but db servers and utilities work)
2. Using configure in the top level directory, configure for your
AFS system type, providing the necessary flags:
% ./configure --with-afs-sysname=sun4x_58 --enable-transarc-paths
+ If you do not have the "configure" script you can re-create it by
+ running regen.sh. You will need autoconf to do this.
+
For some systems you need also provide the path in which your kernel
headers for your configured kernel can be found. See the
system-specific Notes sections below for details.
Be prepared to provide the switches --enable-obsolete and
--enable-insecure if you require the use of any bundled but obsolete
- or insecure software included with OpenAFS. See README.obsolete and
- README.insecure for more details.
+ or insecure software included with OpenAFS. See README.OBSOLETE and
+ README.SECURITY for more details.
+
+ There is an option to control whether or not binaries are stripped
+ of their symbol table information. All binaries, except for the
+ 'fileserver' and 'volserver' executables, are stripped by default.
+
+ To prevent stripping, specify the '--disable-strip-binaries' option on
+ the ./configure command line.
+
+ This option works alongside the existing --enable-debug option to
+ control how binaries are produced. When --enable-debug is specified,
+ binaries will not be stripped. This behavior can be modified by
+ using different combinations of --enable-debug and --enable (or
+ --disable)-strip-binaries. One can, for example, compile binaries for
+ debug and strip them anyway. Alternatively, one can compile without
+ debug and force the binaries to not be stripped. Note that these
+ combinations are not necessarily useful.
+
+ If neither of these options is specified, the default will be to build
+ non-debug binaries that are stripped (with the exceptions noted above,
+ which are never stripped at present). Specifying --enable-debug also
+ turns on --disable-strip-binaries. These are the most useful settings.
+
+ The two binaries noted above, 'fileserver' and 'volserver' will never
+ be stripped, regardless of any options given to configure.
There are two modes for directory path handling: "Transarc mode" and "default mode":
- In Transarc mode, we retain compatibility with Transarc/IBM AFS tools
F OpenBSD Notes
+ We recommend you build with the following options to configure:
+ --enable-namei-fileserver
+ --enable-largefile-fileserver
+ --enable-supergroups
+ --with-krb5
+
You need kernel source installed to build OpenAFS. Use the
--with-bsd-kernel-headers= configure option if your kernel source is not
in /usr/src/sys.
The FreeBSD client is very new and untested. Do not trust it for
production work.
+ We recommend you build with --enable-namei-fileserver and
+ --enable-largefile-fileserver options.
+
You need kernel source installed to build OpenAFS. Use the
--with-bsd-kernel-headers= configure option if your kernel source is not
in /usr/src/sys.
git://git.openafs.org / openafs.git / blobdiff