alpha_dux50 (only tested on 5.0A, does not work with 5.1)
i386_fbsd_42, i386_fbsd_43, i386_fbsd_44, i386_fbsd_45,
i386_fbsd_46, i386_fbsd_47, i386_fbsd_50, i386_fbsd_51,
- i386_fbsd_52, i386_fbsd_53, i386_fbsd_60
+ i386_fbsd_52, i386_fbsd_53, i386_fbsd_60, i386_fbsd_61
+ (client does not work)
i386_linux22, i386_linux24, i386_linux26
i386_umlinux22, i386_umlinux24
i386_obsd31, i386_obsd32, i386_obsd33, i386_obsd34, i386_obsd35,
- i386_obsd36, i386_obsd37, i386_obsd38
+ i386_obsd36, i386_obsd37, i386_obsd38, i386_obsd39
rs_aix42
sgi_65 (file server not tested)
sun4_413 (No client support, no fileserver support, db servers only)
--enable-namei-fileserver
--enable-largefile-fileserver
--enable-supergroups
- --with-krb5
+
+ If you need to run regen.sh to make the configure script, you should
+ first install autoconf-2.59, then setenv AUTOCONF_VERSION 2.59.
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.
- There is a package builder in src/packaging/OpenBSD. "sh buildpkg.sh"
- should make a package for the client. Use pkg_add to install. The
- package will install using transarc-paths, regardless of how you
- configured. The package builder does not work on OpenBSD 3.5 and later
- due to the incompatible re-write of pkg_create.
+ If you want to build src/aklog, "setenv KRB5LIBS -lcrypto" and configure
+ with "--with-krb5". Note that you shouldn't need aklog because heimdal
+ afslog does (almost) the same thing.
- There is no server package, but I am told that "make install" will put
- server binaries in /usr/afs.
+ src/packaging/OpenBSD/buildpkg.sh will make a tar file for installing the
+ client. There is no server package, but I am told that "make install"
+ will put server binaries in /usr/afs.
Your kernel may panic when you try to shutdown after running the OpenAFS
client. To prevent this, change the "dangling vnode" panic in
G FreeBSD Notes
- The FreeBSD client is very new and untested. Do not trust it for
- production work.
+ The FreeBSD client does not currently work. The remaining problems
+ mostly have to do with locking, vnode refcounting, and packaging. The
+ server should work.
We recommend you build with --enable-namei-fileserver and
--enable-largefile-fileserver options.