Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!bbn!uwmcsd1!ig!jade!ucbvax!ftp.UUCP!jbvb
From: jbvb@ftp.UUCP (James Van Bokkelen)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: Misc. Problems with CMU/PC-IP
Message-ID: <8710281546.AA11676@spdcc.COM>
Date: Wed, 28-Oct-87 10:08:59 EST
Article-I.D.: spdcc.8710281546.AA11676
Posted: Wed Oct 28 10:08:59 1987
Date-Received: Sat, 31-Oct-87 09:02:46 EST
References: <8710280218.aa07867@Louie.UDEL.EDU>
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 20

Regarding local host tables:  As far as I know (I haven't used a number
of the Public Domain packages), all of the commercial offerings have
hosttable facilities, and none of the free ones do.  We put our own
in when we started using our package internally, but couldn't afford
anything we could run a standard nameserver on.

Regarding your question 3: It is more or less a "feature" that our 1.16
(and most other descendants of PC/IP) co-exists with CMU.  Each of the
programs has its own hardware driver and interrupt service, and tries to
be well-behaved in how it leaves the interface and vector (although versions
of the Stanford code of a year ago apparently didn't restore the vector).

We sell a $40 "Public Domain Software" diskette that has an IEN-116 nameserver
on it (in source form for 4BSD systems).  We've been told that we could
put Berkeley's Bind on the same diskette, but it is quite large, even
when compressed.  Either program can also be picked up by anonymous FTP
from various Internet sites.

James B. VanBokkelen
FTP Software Inc.