A PAM module to call setpag and run aklog. Based on ideas by Sam Hartman
and Doug Engert. Probably doesn't yet do everything that we want and needs
more eyes, but it at least builds.
Overhaul how we build shared libraries. Pull the code for building and
installing shared libraries out into simple shell scripts that we can then
evolve as we need to and make more sophisticated. Remove the details of
how to use a mapfile from the Solaris Autoconf-driven configuration and
move them to the Solaris case of the build script. In the process, make
it possible to build more than one shared library in a single directory.
Remove the last vestiges of libafssetpag from the sys directory; kopenafs
now replaces all of that.
Only link in syscall.o in the sys and kopenafs directories on those
platforms that actually care so that we don't have to do work to generate
a valid .o file that can be included in an archive.
Take advantage of the new platform infrastructure to move fs_conv_sol26 out
of the vol directory and remove the annoying Autoconf support for
optionally build it in favor of the platform support. We no longer care
about upgrading inode file servers on DUX, so make fs_conv_DUX4 go away.
Add a shared libkopenafs that provides k_hasafs, k_setpag, k_unlog, and
k_pioctl (in other words, enough for a PAM session module that calls an
external aklog).
Modify vice.h so that it doesn't depend on afs/param.h. Split the VIOC*
constant definitions out of afs/venus.h into a separate header file
included by it. Update various comments to reflect a more recent version
of reality. This is in preparation for kopenafs work so that kopenafs.h
can include afs/vioc.h as well to get the same definitions.
Remove the preliminary rxgk and Automake conversion, neither of which are
finished or ready for prime time yet. Having this active in CVS isn't
helpful and is mildly confusing at the moment.
Remove files that were only used for the DOS or Windows 95/98 ports,
both of which are completely obsolete. Also remove InstallShield version 5
support.
General consensus is that the termlib hacks that necessitate the libnull.a
hack don't matter on any current platform we build on, and even if it does,
it should be dealt with in TXLIBS in osconf.m4. So remove all of that
infrastructure and see what fails.
Remove README.SECURITY given that we've already removed all the code that
it was talking about. Remove references to README.OBSOLETE, since it's
now gone.
Delete pinstall and convert the entire tree to use the install program
found by configure (falling back on install-sh in the local tree). This
means that we have to pre-create directories with install -d. Also redo
the install and dest rules to be lists of install rules rather than
dependencies driving separate make rules so that running make install will
always update the target directory with the current code, even if there are
files in the install area that are newer.
Stop installing libafssetpag; we're about to kill it in favor of a
different library. Remove some djgpp rules.
FIXES 36646
nfs translator for linux, plus xen support for shared afs client
====================
This delta was composed from multiple commits as part of the CVS->Git migration.
The checkin message with each commit was inconsistent.
The following are the additional commit messages.
====================
FIXES 36646
add linux afs translator plus xen shared afs client support
====================
FIXES 36646
add linux afs translator plus xen shared afs client support
====================
FIXES 36646
add linux afs translator plus xen shared afs client support
Rewrite the aklog man page in POD and add documentation of the new flags
and .xlog.
====================
This delta was composed from multiple commits as part of the CVS->Git migration.
The checkin message with each commit was inconsistent.
The following are the additional commit messages.
====================
Fix my misunderstanding of what rxkad2b is.
====================
Fix unterminated B<>.
However, in bucoord/commands.c, bc_VolRestoreCmd(), bc_DiskRestoreCmd(),
bc_VolsetRestoreCmd(), and bc_DumpCmd() were passing '0' as arguments
instead of NULL. Because there is no prototype for bc_StartDmpRst() this
results in a crash on 64-bit Linux. (when running 'volrestore' from an
interactive backup session)
