Path: utzoo!attcan!uunet!husc6!bloom-beacon!think!ames!pacbell!rtech!wrs!hwajin
From: hwajin@wrswrs.UUCP (Hwajin Bae)
Newsgroups: comp.protocols.tcp-ip
Subject: Re: RPC Library sources for System V
Keywords: RPC System V
Message-ID: <647@wrs.UUCP>
Date: 8 Jun 89 18:30:02 GMT
References: <457@focsys.UUCP> <111@xicom.UUCP>
Reply-To: hwajin@wrs.UUCP (Hwajin Bae)
Organization: Wind River Systems, Emeryville, CA
Lines: 27

In article <111@xicom.UUCP> alex@xicom.UUCP (Alex Laney) writes:
>
>	RPC is a standard part of NFS, no? I recall (faintly) somewhere that
>Interactive advertised this as part of their NFS product.
>
>	I have a copy of their Host-based TCP-IP, and the RPC3.9 source code.
>My experience is that with modification of the headers, I could get it to
>compile, but it would crap-out at run-time. This was a few months ago, so I
>don't recall the exact error. I will be trying again soon, however.

If you have their NFS for the SVR3 UNIX and TCP/IP (probably Lachman derived),
you should be able to use RPC3.9 with minor modifications.  

RPC implementation is, in a way, duplicated in most Unix implementations
-- the one in the kernel code which is being used by NFS and linked 
into the kernel itself usually and the one that is provided as user
level library for application use.  Since RPC library used in normal
application programs are built entirely on top of socket library you
should have no problem if you have a compatible 4.3 BSD TCP/IP and socket
library with your system, which I assume you do.  If your TCP/IP doesn't
implement all necessary socket calls, socket options, and ioctl's 
you may run into some problems.  What kind of modifications did you have
to make to the header files?


-- 
{uunet,rtech,sun}!wrs!hwajin  bae@tis.llnl.gov  hwajin@wrs.com