ordering of dependancies caused ${DESTDIR}/include/afs to not exist in
time, masked if you built into an existing destdir. so let's make
the makefile simpler and more logically paraallel.
====================
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.
====================
get missing backquote
get rid of cases where we'd end up with two / because of DESTDIR pasting
macroize calls to rm
====================
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.
====================
get rid of another case of bogus trailing quoting
clean up all the makefiles to remove bogus targets, eliminate trailing /
requirement from DESTDIR, avoid needing to pass things like DESTDIR around
between makefiles
====================
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.
====================
remove bogus quoting
1. Version control (Win9x & Windows NT/2000)
NTMakefile.i386_win95 and NTMakefile.i386_nt40 added AFSPRODUCT_VERSION
variable, setting this will propagate through the software by setting
the product version for the installation and client dialog boxes. In
particular it will provide correct notification if Win2K installation is
being upgraded, reinstall or downgraded.
Version information shows up in the following ways:
Welcome dialog during installation
Properities page for Install.exe (Windows Installation routine)
Windows Add/Remove Dialogs application list
AFS Control Center and Client dialog boxes
See README-WIN9X.TXT or README-NT.TXT for further information on how to set thi
s
variable.
2. CellServDB (Win9x & Windows NT/2000)
The installer can choose between various sources for CellServDB:
a) Previous installed file, afsdcell.ini(WinNT/2000) or CellServDB(Win9x).
b) File that comes with the installation package (recent copy from grand.centra
l.org)
c) Download a the file from the Web (default http://grand.central.org/dl/cellse
rvdb/CellServDB).
d) Browse for a file
3. Drive Mapping (Win9x & Windows NT/2000)
The installer can choose up to two drive mappings during the installation
process. Default is map Z: to AFS root and U: to user home directory
4. Silent Running (Win9x & Windows NT/2000)
Setup.exe is capable of running silently (-s option); that is, it will use a pr
e-made
response script to drive its responses. You can also do a normal installation
with
the record option (-r) to build a sample response file.
The installation routine has been improved to accept a modified response file s
o the
administrator can setup up additional drive mappings including substituting the
user's
loggin name into the path. By using a text editor an administrator can setup a
variable
path name that includes %LOGINNAME% in a path statement. This variable will be
substituted for the current user's login name. (Only at installation time.)
For example: if an administrator wanted to install AFS client on a machine that
had the
following mappings:
Z:=/
U:=/afs/afscell.org/u/username
Q:=/afs/afscell.org/general
Then follow these steps:
a) run setup with -r option and specify install to record responses into file s
etup.iss
setup.exe -r -f1setup.iss
b) Follow normal installation responses
c) Edit the setup.iss response file by modifying the "DRIVEPATH section".
This response file could start off looking like this:
[DLG_DRIVEPATH-1]
Result=1
Drive_0=Z:
Path_0=/
Share_0=all
Drive_1=U:
Path_1=/afs/afscell.org/u/administrator
Share_1=home
Count=2
This section map would be changed to look like this:
[DLG_DRIVEPATH-1]
Result=1
Drive_0=Z:
Path_0=/
Share_0=all
Drive_1=U:
Path_1=/afs/afscell.org/u/%LOGINNAME%
Share_1=home
Drive_2=Q:
Path_2=/afs/afscell.org/general
Share_2=genrl
Count=3
d) Use the silent mode to install AFS (must log to windows as your user name e.
g. Frank)
setup.exe -s -f1setup.iss
HINT: Share name should be limited to 12 characters.
The response file terminate if the installation is in any way different; for
example,
the response is recorded on a clean machine and it is run on a system where
AFS
is already installed.
The execution is truly silent, except for a log file.
The last response is BootOption and if set to 1 it will reboot your machine!
Refer to additional documentation on silent/record in you Install Shield User's
Guide.
5. Fixed the Un-Installation bug that damaged the NetBT parameter registration. (Win2k/NT only)
6. Change Default selection for Win2000 to Client and Documentation only. (Win2
K/NT only)
The default installation is with Server and Control Center NOT selected.
7. Win9x Client Operation (Win9x only)
Win9x client has been changed to allow "connection" with out forcing
authentication. Previous implementation of the Win9x client had three steps to
the
connection process: 1) start client 2) obtain tokens 3) Map drives
The updated Win9x client can leave the username blank and select to Connect. T
herefore, only
the client will be started (without obtaining tokens). The user can still map
drives
(those that don't require authentication). This is particularity useful if you
want to
use a different routine to obtain authentication tokens or additional drive map
pings.
A command line option has also been added (-noid). This option Prevent selecti
on of
(Gray out) username/password. This will cause the client to start up without au
thentication.
By using both -noid and -connect allows the user to run the AFS client in login
script
that could provide Kerbos 5 authentication and addition drive mapping.
8. Installation (Win9x only)
Fix installation into paths that have space, e.g. \Program Files\Afscli
====================
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.
====================
complete list in first message
bcopy, bcmp, bzero, index, rindex, you're all cut.
memcpy, memcmp, memset, strchr, strrchr, show us how it's done
====================
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 reference to memset the right thing
====================
make change to arguments globally and not just for e.g. linux/darwin/fbsd
====================
fix a minor flub in how this was done
====================
correct another bad memcpy coversion
====================
fix up more inadvertant turds
====================
fix two errors found by chas williams
"no special instructions this time other than you need a rather recent
glibc (turbolinux beta5 or redhat 7.1) since the afs userland utilities
use ucontext() instead of setjmp()/longjmp(). this is probably the weakest
part of the port since lwp is somewhat difficult to test rigorously.
you can insmod the afs module now (and rmmod if you like) why so difficult?
function pointers are really pointers to a function descriptor that contains
the function pointer and global pointer. the syscall table (being written
in assembler) only contains function pointers. it doesnt setup the gp.
modules and kernels do not share the same gp. so if you want the syscall
to go to a module, you need to setup the gp and then call your module's
routine. be sure to restore the gp after returning from your routine :)
i also converted to the 'new style' module_init() -- only used on kernel
versions 2.4.0 and up. this does the right thing if you happen to be
linked directly with the kernel.
klog has been fixed (afs's crypt() function is sensitive to sizeof(long) --
des/crypt.c should probably use 'afs_int32', not 'long' or 'int')
in case it matters, my platform is a b3-stepping running beta5 of turbolinux."
====================
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.
====================
don't leak into not ia64 port
note gi is useless for namei case
The AFS_64BIT_ENV define is needed for afsutil.h which makes use
of some 64-bit types (and if AFS_64BIT_ENV isn't set, defaults to
the non-existant u_int64_t).
convert rest of source to afsconfig; include rcsid macros
====================
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.
====================
remove bogus if/define/endif triple
====================
revert non-rcsid and afsconfig portion of patch
replace existing build system with autoconf faceplate
====================
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.
====================
so we can fix the file modes
====================
commit withj correct file modes
====================
stuff which got left behind
====================
more stuff which was missed
====================
get this right so build completes
====================
also make these correct (no obj reference)
====================
so autoconf dependancy chain need not change
====================
set correct variable for obsolete buildng
====================
so we can more easily use autoconf'd CC var
updates for nt/2000 and 95/98 afs clients
====================
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.
====================
binary file updates
"This patch implements AFSDB support for both user-space programs
and for the kernel.. I've tested these on sun4x_57 (64-bit) and
on i386_linux22."
not currently enabled in any configuration
Windows 95/98 port from IBM Almaden
documentation and build support
====================
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.
====================
Windows 95/98 port from IBM Almaden
changes to cache manager
====================
Windows 95/98 port from IBM Almaden
makefile changes
====================
Windows 95/98 port from IBM Almaden
osi changes to support 95/98
====================
Windows 95/98 port from IBM Almaden
installer for 95/98 client
====================
Windows 95/98 port from IBM Almaden
win95/98 panel app
====================
Windows 95/98 port from IBM Almaden
win95/98 panel app help
====================
Windows 95/98 port from IBM Almaden
makefile changes plus dns implementation
====================
Windows 95/98 port from IBM Almaden
makefile changes plus changes for compat with dos line conventions
====================
Windows 95/98 port from IBM Almaden
config for 95/98
====================
Windows 95/98 port from IBM Almaden
makefile changes plus support for 95/98 env
====================
Windows 95/98 port from IBM Almaden
ms compiler changes
====================
Windows 95/98 port from IBM Almaden
makefile changes
====================
Windows 95/98 port from IBM Almaden
lwp changes
to support 95/98 port
====================
Windows 95/98 port from IBM Almaden
rx changes to support 95/98 port
It turns out defining AFS_64BIT_ENV ends up causing accesses to hang
if a server goes down; Should not be the case but other work will be needed
to figure out why or even if we need to be AFS_64BIT_ENV; in the meantime,
revert this part of patches done for xdr_int64; it's not ncessary now anyhow
setup for darwin port
====================
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.
====================
changes for darwin port
====================
added files for the darwin port
====================
changes for darwin port
Changes for Alpha to previous 64 bit changes for sparc (sparc64 isn't
necessarily analogous to alpha or any other 64 bit linux platform)
====================
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.
====================
use mkstemp
====================
Include necessary file for alpha config
====================
Deal with 64 bit time_t
====================
Don't do increments in a way that can be miscompiled
====================
configure for alpha linux
====================
deal with time and initialize a variable
====================
don't use ViceIoctl32 for alpha linux
====================
deal with compiling kdump for alpha linux
====================
mods in callback.c analogous to dux port; mods in viced to deal with
thread creation function return convention
====================
config for linux alpha
====================
ids for alpha linux consistent with new-style sysname grouping
====================
makefile and config files for new-style sysnames
====================
MakefileProto changes for alpha linux with new-style sysnames. A change
in config/mc.c will be needed for this to configure correctly, and it will
be added soon
====================
note alpha port and the state it's in to hopefully avoid questions
" Extensions used by MR-AFS in the client. I have added only two
pioctl-calls which are used by the "fs"-command for a large number
of MR-AFS specific subcommands. With this modification also the
data type afs_int64 is introduced because MR-AFS supports large files.
afs_int64 is either "long long" or a structure consisting of two
32-bit numbers. We are already running on rs_aix42 a fully large-file
capable AFS-client, but these changes are still in a beta test and
not yet added here."
