Path: utzoo!attcan!uunet!super!udel!gatech!uflorida!mailrus!sharkey!atanasoff!jwright
From: jwright@atanasoff.cs.iastate.edu (Jim Wright)
Newsgroups: comp.sys.amiga
Subject: Re: Dnet and HP-UX?
Message-ID: <720@atanasoff.cs.iastate.edu>
Date: 22 Jan 89 08:40:54 GMT
References: <2807@hplabsz.HPL.HP.COM> <6080013@hpcupt1.HP.COM> <2255@uokmax.UUCP> <199@nlgvax.UUCP>
Reply-To: jwright@atanasoff.cs.iastate.edu (Jim Wright)
Organization: Iowa State U. Computer Science Department, Ames, IA
Lines: 16

In article <199@nlgvax.UUCP> hans@nlgvax.UUCP (Hans Zuidam) writes:
>The HP9000 Series 500 do have a socket like mechanism. They are called
>virtual circuits. Their functionallity is almost the same as that of 4BSD
>TCP sockets. As far as I can remember the function calls all started with
>"vc_". As a requirement you do need to have the Remote File Access and ??
>(can't remember that one) software that comes (came?) with the ethernet
>interfaces.

It should be noted that a "socket-like" mechanism, or even some sort of
socket, may not be enough to run DNet.  DNet uses "Unix internal format"
sockets.  What you describe sounds like an emulation of internet sockets.
On the Apollo with SR9.7 (the source of my woes), the only supported socket
is internet protocol.  So just having somebody's idea of a socket in your
system may not get you where you want to go.

Yes, you could modify the source, but you could also port it to Sys.V.  :-)