Skeletal instructions for using the contents of this tar file
		(for libupd 1.0a.  WJS.  Sep 04)

	libupd is a release of files found in jgofs.a that I know to be
different from versions of those files released with the jgofs 1.5
release.  It also includes files released after jgofs 1.5.
	It also contains .h files, and updates "the include" directory
with those files

Most straightforward way to update jgofs.a & various include files:
	1) cd to the library directory (usually jgofsroot/src/lib)
	2) backup this directory to your satisfaction.
	3) backup ../include to your satisfaction.
	4) unpack this tar file.  It will replace versions of .c
	   and .h files, as well as replace earlier versions of
	   support files that may have been included in previous
	   libupd releases
	5) check the dates on httcp.c (which came from the tar file)
	   and HTTCP.c.  If httcp.c is in fact newer, be sure its
	   date is more recent (touch httcp.c if necessary)
	6) compare _makefile_.jgofs with makefile.jgofs
	   Note that _makefile_.jgofs compiles everything w/debug support
	      You may wish to change this
	   The 2 make files should be functionally the same unless:
	      a) a file in your jgofs.a library is not included in
		 libupd
	      b) a file in your jgofs.a library is compiled differently
	 	 from the way libupd compiles its version
	   I believe a) is not a fatal problem because my understanding
	      of ar, the program which builds jgofs.a, is that with
	      the switches typically set in jgofsroot/build-env, ar
	      will update jgofs.a, overwriting modules if needed.
	   b) is a problem
	7) replace makefile.jgofs with _makefile_.jgofs after suitable
	   modification
	8) If you have build.pl
		jgofsroot/build.pl lib
	     or
		jgofsroot/build-env.pl -sh > /tmp/envvars
		source /tmp/envvars
		make -f src/lib/makefile.jgofs
	   If you do not have build.pl
		cd jgofsroot
                ./build lib
	     or
		cd jgofsroot
		/bin/csh
		source build-env
		make -f src/lib/makefile.jgofs
		exit

Files:
	This tar file contains most of the files released with jgofs 1.5,
as well as files which seem to have ended up in jgofs.a anyway.  The only
2 .c files I know of that are in jgofs.a and NOT in libupd are HTParse.c
and HTString.c.  A list of the libupd .c files is included at the end of
this file.
	This tar file also contains 2 "stub" files containing 
rudimentary err routines.  Most of the jgofs.a routines now call err to
report their problems.  It is intended that main programs calling the
library provide an err entry to handle problems reported by the
library (as well as, presumably, their own).  For old programs whose
source we may not want to change, err_stub.o or err_stub_methods.o
can be added into the appropriate make file.  err_stub_methods should
be used w/inners; err_stub w/stand-alone programs.  See their .c files
for more comments, etc.
	_makefile_.jgofs can be used to build a test jgofs.a file where
desired.  A sample that builds ./jgofs.a on the globec data server is
included as c shell script make_testjgofs.csh.  The name, directory, or
both, of the output library can be changed by specifying 
LIBNAME, LIBDIR, or LIB, respectively, on the make command.
	HTTCP.c is included as httcp.c.  The make file renames things
appropriately if the dates work.  If HTTCP.c "arrived" via cp, its
date may be newer than that of httcp.c in a tar file, despite the
contents being older.
	This tar file also contains core.h, path_info_routines.h, and
utils.h.  The make file included in this tar file will place these
.h files in ../include (unless existing files in ../include are newer)
To complete a usable library, the system maintainer is responsible for
the creation and contents of ../include/default.h and 
../include/inner.h

  library .c files included in libupd 1.0
dct.c
jdb.c
httcp.c
outer_utils.c
path_info_routines.c
startchild.c
utils.c