Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!watmath!clyde!rutgers!seismo!mcvax!ukc!dcl-cs!strath-cs!jim From: jim@cs.strath.ac.uk (Jim Reid) Newsgroups: net.dcom,net.micro.hp Subject: Re: Looking for TCP/IP for HP9000 running HP/UX Message-ID: <299@stracs.cs.strath.ac.uk> Date: Fri, 31-Oct-86 05:10:20 EST Article-I.D.: stracs.299 Posted: Fri Oct 31 05:10:20 1986 Date-Received: Wed, 5-Nov-86 06:17:25 EST References: <171@gt-eedsp.UUCP> <1226@hoptoad.uucp> Reply-To: jim@cs.strath.ac.uk (Jim Reid) Organization: Department of Computer Science at Strathclyde University, UK. Lines: 35 Xref: watmath net.dcom:2202 net.micro.hp:318 In article <1226@hoptoad.uucp> gnu@hoptoad.uucp (John Gilmore) writes: >In article <171@gt-eedsp.UUCP>, deb@gt-eedsp.UUCP (Deb Jackson) writes: >> We've got 2 HP-9000's (300 series) running HP/UX, with ethernet. >> The problem is that the HP's don't have TCP/IP, so we've got a >> real problem trying to get them to talk to our Vax running 4.2BSD(BRL). > >The October 86 issue of the HP Journal just arrived here last week. >It's all about networking and HP's AdvanceNet architecture. Turns >out that they *did* implement TCP/IP on the HP 3000 series, but the >HP 9000's have to suffer with HP proprietary protocols for file transfer >and remote file system access. No standard protocols are provided, >except that if you really want to, you can read and write raw Ethernet >packets (gee thanks!). You could probably cobble something together >to talk to your Vaxen this way. > >Hard to believe that they did all the development to build TCP/IP on >the 3000's, but for Unix, where an implementation was available for free, >they didn't bother... Yes, this is very annoying. We have just bought a 9000/560 series which has no Ethernet software at all. [We bought the machine because it's ideal for one of our teaching labs as a "standalone" machine.] We have been told that HP are paying the Wollongong (sp?) Group to port the BSD TCP/IP software to this beast. This is crazy when as John Gilmore says HP could have had the code for nothing. [OK SysV != BSD, but it shouldn't be *that* much work.] Instead, we have to wait for a third party to develop and provide the code. Meantime, we're itching to add the machine to our network. Jim ARPA: jim%cs.strath.ac.uk@ucl-cs.arpa, jim@cs.strath.ac.uk UUCP: jim@strath-cs.uucp, ...!seismo!mcvax!ukc!strath-cs!jim JANET: jim@uk.ac.strath.cs "JANET domain ordering is swapped around so's there'd be some use for rev(1)!"