[comp.sys.sun] RPCSRC 4.0 now available from titan.rice.edu

sxn@sun.com (Steve Nahm) (02/02/90)

RPCSRC 4.0 is finally available in the sun-source directory on
titan.rice.edu.  You should be able to retrieve it through anonymous FTP
and via the archive-server.

RPCSRC 4.0 was released in November of 1988 and has been available from
other sources for some time (such as the NFS archive at bcm.tmc.edu).
This release was based on the FCS version of the SunOS 4.0 RPC library;
the previous release, RPCSRC 3.9, was based on the SunOS 4.0 Beta RPC
library (and 3.9 also did not include any Secure RPC code).

There are three sets of shar files associated with this release.  The
files that start with "rpc-39_40.XX" (where XX is 01 through 03) are patch
files that will upgrade RPCSRC 3.9 to RPCSRC 4.0.  "secure_rpc.XX" (where
XX is 01 through 04) is the Secure RPC code and documentation (with the
exception of the DES algorithm).  rpc_40.XX (where XX is 01 through 17) is
the full RPC library (with the exception of Secure RPC).  So, people who
do not have RPCSRC 3.9 should retrieve all of the rpc_40 files, and the
secure_rpc files if that code is desired.  (Since DES is not included in
this distribution, Secure RPC will not work unless you provide a DES
algorithm, or one is available on your system).

For more information about RPCSRC 4.0, please see the README files
included with the release.

For your information, I am working on the next release of RPCSRC, which
will be the Transport Independent RPC implementation.  TI RPC is included
in System V, Release 4, and uses the Transport Level Interface (TLI)
rather than sockets (which are used in RPCSRC 4.0).  I expect to post this
to the net at the end of March.

Steve Nahm
Distributed Systems Software

[[Ed's Note: placed in archive <finally :(> Also: anyone that wants to use
FTP to send source files directly to Rice, please feel free to do so;
however, you need to also send a note to sun-spots@rice.edu explaining
what exactly it is and letting me know that it has been placed in the
incoming directory. We can accept sources this way, but I do not regularly
check the incoming directory. -bdg]]

FTP: 	Hostname : titan.rice.edu (128.42.1.30)
	Directory: sun-source
	Filename : rpc_39-40.{01-04}
		   rpc_40.{01-17}
	 	   secure_rpc.{01-04}

Archive Server Address: archive-server@rice.edu
Archive Server Command: send sun-source {filename_from_above}