This file:
/afs/hackathon.openafs.org/user/mdw/afs-rxk5-merge-v83.patch.bz2
also here:
/afs/umich.edu/group/itd/build/mdw/tmp/afs-rxk5-merge-v83.patch.bz2
is a copy of the latest "stable" match from Matt and I.
This does NOT include using "afs-k5/[EMAIL PROTECTED]", but does
do:
        rxk5 
        on linux
                either uml or native
                2.4 or 2.6
                fileserver, cm, ubik, userland tools, & all
        using "heimdal-20060410"
it should also build without rxk5, & at runtime, will select
rxkad and/or rxk5 for the server side stuff depending on the
preseence or absence of "/etc/openafs/server/afs.keytab"
(which if present should contain an instance of "[EMAIL PROTECTED]").
Basic functionality should all be there, there are almost
certainly rough edges & weirdness.

When I built this, I used:
/1/ heimdal-20060410:
./configure --prefix=/usr/local/heimdal-k5-20060410 --disable-pthread-support
Heimdal thinks it's using the compile_et & libcom_err that comes from
e2fsprogs 1.38.

/2/ openafs-1.4.1 + the above patch, then
afslogsdir=/var/log/openafs \
sh configure \
        --with-linux-kernel-headers=/usr/src/linux-2.4.26 \
        --with-afs-sysname=i386_linux24 \
        --enable-supergroups \
        --enable-fast-restart \
        --enable-bitmap-later \
        --enable-rxk5 \
        --prefix=/usr \
        --sysconfdir=/etc \
        --libexecdir=/usr/lib \
        --disable-kernel-module \
        --localstatedir=/var/lib \
        --with-linux-kernel-headers=/usr/src/linux-2.4.26 \
        --with-krb5-conf=/usr/local/heimdal-k5-20060410/bin/krb5-config
for reasons related to local environment weirdness (heimdal's
location) and a vague belief that the debian folks understand
FHS (openafs).

Some issues that I believe remain:
* building with anything but linux.
        (should be trivial, but I know they exist.)
* comerr stuff. (but this version does export _et_list).
* being smarter about building with more flavors and
        configurations of heimdal.
* afs-k5, localauth & all that.
* don't use -L to locate static libraries at build time.
* things I don't know or can't recall even having just drunk
        some excellent jasmine tea.

                                -Marcus
_______________________________________________
OpenAFS-devel mailing list
[email protected]
https://lists.openafs.org/mailman/listinfo/openafs-devel

Reply via email to