home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.hp
- Path: sparky!uunet!ukma!darwin.sura.net!ra!atkinson
- From: atkinson@itd.nrl.navy.mil (Randall Atkinson)
- Subject: Re: Re: HPUX & SVID
- Message-ID: <Bxw56M.F9C@ra.nrl.navy.mil>
- Sender: usenet@ra.nrl.navy.mil
- Organization: Naval Research Laboratory, DC
- References: <BxLv9F.tB@ra.nrl.navy.mil> <4310312@hpindda.cup.hp.com>
- Date: Wed, 18 Nov 1992 02:49:33 GMT
- Lines: 32
-
- In article <4310312@hpindda.cup.hp.com> alech@hpindda.cup.hp.com (Alec Henderson) writes:
-
- >HP has just released a separate STREAMS/UX product. It requires HP-UX 9.x.
- >It includes the basic STREAMS framework, a generic TLI interface, and
- >DLPI to HP's Ethernet/802.3 and Token Ring/802.5 network interface
- >cards.
- >
- >The STREAMS/UX product does NOT provide a STREAMS-based implementation
- >of pipes and fifos, TCP/IP, or terminal I/O.
-
- This is a step in the right direction.
-
- A comment:
- Longer term, I'd like to be able to use the STREAMS interface and
- modules I'm used to with pipes and fifos and terminal i/o also. I
- don't particularly care how you build your kernel internals as long as
- I can use STREAMS on HPUX the same way I can use it on my more modern
- versions of System V (i.e. I want source code compatibility) .
-
- A question:
- What does it mean to say that HP provides "a generic TLI interface"
- but does "NOT provide a STREAMS-based implementation of TCP/IP" ??
-
- Does this mean that I get TLI without any protocols underneath the
- interface ?
-
- Or does this mean that internally underneath you guys are translating
- STREAMS+TLI into sockets calls in a way that I don't need to care
- about ??
-
- Ran
- atkinson@itd.nrl.navy.mil
-