Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: Notesfiles $Revision: 1.6.2.17 $; site ccvaxa.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!ihnp4!inuxc!pur-ee!uiucdcs!ccvaxa!preece
From: preece@ccvaxa.UUCP
Newsgroups: net.unix-wizards
Subject: Re: Is 4.2BSD a failure?
Message-ID: <47500007@ccvaxa.UUCP>
Date: Wed, 23-Jan-85 10:09:00 EST
Article-I.D.: ccvaxa.47500007
Posted: Wed Jan 23 10:09:00 1985
Date-Received: Fri, 25-Jan-85 07:42:53 EST
References: <17100032@wdl1.UUCP>
Lines: 20
Nf-ID: #R:wdl1:17100032:ccvaxa:47500007:000:1061
Nf-From: ccvaxa!preece    Jan 23 09:09:00 1985

>				...  The most significant addition was the
>	support for networking, which may be the last gasp of the
>	networking-inside-the-operating-system approach.  (The state of the
>	art is to use intelligent networking cards; Excelan and Communications
>	Machinery make cards that provide IP/TCP services on an Ethernet;
>	these cost about the same as ordinary dumb Ethernet cards.)
----------
Leaving aside thoughts of how nice it would be to be able to afford to
replace all our equipment with state of the art boards, how about those of
us with machines other than Vaxen?  Curiously enough, the board manufacturers
don't hit the street with boards for every machine all at the same time.
The Berkeley networking code allows access to generic sorts of ethernet
controllers which may be easier to put together for another machine.
The next generation will have intelligent components, but for now it's
nice that all our little machines (and our big ones) have been able to
talk to each other through the Berkeley code.

scott preece
ihnp4!uiucdcs!ccvaxa!preece