Path: utzoo!mnetor!uunet!lll-winken!lll-lcc!mordor!lll-tis!ames!ptsfa!pbphb!pbhyf!tlh
From: tlh@pbhyf.UUCP (Lee Hounshell)
Newsgroups: comp.sys.att
Subject: SOCKETS? (was Re: Query about the quality of UNIX/PCs and 3b1's)
Message-ID: <2603@pbhyf.UUCP>
Date: 28 Dec 87 18:41:28 GMT
References: <9691@shemp.UCLA.EDU> <18017@clyde.ATT.COM> <997@bakerst.UUCP> <1146@mtunb.ATT.COM> <2420@oxtrap.UUCP> <2208@crash.cts.com>
Reply-To: tlh@pbhyf.UUCP (Lee Hounshell)
Organization: Pacific * Bell, San Ramon, CA
Lines: 15

In article <2208@crash.cts.com> ford%kenobi@crash.CTS.COM (Michael Ditto) writes:
>It also has some minor extentions from both System
>V Release 3 and Berkely Unix.  For example, from SVR3 comes the "xt"
>multiplexing protocol and "layers" windowing system, and internal support
>for the "Streams" I/O system.  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