This file contains the directions to install the AFS client on an OS/2
machine.  These directions assume that you already have installed
TCP/IP.


All the lines in the file \afs\bin\initfile.afs , following the fifth
line define drive designators for AFS directories.  Each line is in
the following form:

    drive: \afsDir1\afsSubDir1\afsSubDir2\...\afsSubDirN

The colon must follow the drive designator.  The AFS path must be a
complete path, ending in a directory name (NOT a file name).  The next
time that venus is started, that AFS directory will be associated with
that drive designator.

Some general comments about the OS/2 AFS client.
We assume that the user already has the Transarc AFS documentation.
What is contained here are special features that only apply to OS/2.

venus.exe - this is the client executable. It can be invoked in the
same manner that any other OS/2 executable is invoked. The only option
supported is the "-rootvol" option. This option is used to designate
which volume should be used by the client as the root volume. The
default root volume is the root.afs volume.

klog - the kerberos authentication program. This program is used to
authentication to AFS. This is a standard klog program as defined in
the Transarc manuals. The only options supported are the "-x", the
"-password"  and "-cell" options. 

drvattch.exe - to manually attach a drive, issue the drvattch
command. This command takes 1 or 2 arguments. The first argument is
mandatory. It is a drive designator (i.e. "f:"). The second argument
is optional. It is the pathname to be associated with the drive. For
instance, you can issue "drvattch f: \graysland.ibm.com\u\ogle". This
will associate the user subdirectory ogle with the f: drive. Thus
doing a dir on f: will only show files in \graysland.ibm.com\u\ogle.



