Path: utzoo!mnetor!uunet!husc6!hao!oddjob!gargoyle!ihnp4!laidbak!spl1!richp1!emike
From: emike@richp1.UUCP (E. Mike Durbin)
Newsgroups: comp.sys.att
Subject: Re: SOCKETS? (was Re: Query about the quality of UNIX/PCs and 3b1's)
Message-ID: <45@richp1.UUCP>
Date: 29 Dec 87 14:26:25 GMT
References: <9691@shemp.UCLA.EDU> <18017@clyde.ATT.COM> <997@bakerst.UUCP> <1146@mtunb.ATT.COM> <2420@oxtrap.UUCP> <2208@crash.cts.com> <26
Reply-To: emike@richp1.UUCP (E. Mike Durbin)
Organization: Rich Inc., Chicago
Lines: 38

In article <2603@pbhyf.UUCP> tlh@pbhyf.UUCP (Lee Hounshell) writes:
>In article <2208@crash.cts.com> ford%kenobi@crash.CTS.COM (Michael Ditto) writes:
>>                               From BSD comes the Berkeley network socket
>>capability, although this is only included with the Ethernet software.
>
>Does this mean that my 3B1 kernel is capable of supporting Berkeley socket
>calls?  If so, I could run a *whole bunch* of public domain software that
>was written using sockets as an IPC mechanism!  Does anyone out there know
>how to access it?  Or do I need to first get this Ethernet software ($$ ?)
>Similarly, is it possible to access the streams system and/or create new
>drivers using it?  If you're reading this, AT&T/Convergent, why didn't you
>include the librarys/documentation needed to use these tools with the 3B1?
>
>Lee Hounshell

Mike Ditto exaggerates (a little).  The loadable device driver for
TCP/Ethernet includes the socket interface and kernel routines.  A
user level socket library in provided also (libnet.a I believe).  The
loadable device driver for Starlan includes the Streams routines.  I
don't remember any libraries, documentation, or tools for Streams.

Neither Sockets or Streams are part of the 3B1 kernel, both are provided
with (loadable) device drivers.

Also, you need a minimum of 2.5 Meg of RAM to run both Ethernet and Starlan.
You also have to load Ethernet FIRST.  Both dynamically allocate kernel heap
after being loaded, but only Starlan checks if the allocation failed.  If
you load Ethernet first, and the kernel heap allocation fails, the system
will hang.  (Actually, the Ethernet driver blocks waiting for heap to be
freed, which will never happen, as the machine isn't even up yet).

See /etc/lddrv/drivers (if I remember correctly) for the order in which
the drivers are loaded.
-- 
------------------------------------------------------------------------------
             ...!cuuxb \		E. M. Durbin
		        !richp1!emike	Rich Inc.
...!ihnp4!laidbak!spl1 /		Chicago