home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.unix.sysv386:13206 comp.unix.wizards:3631
- Newsgroups: comp.unix.sysv386,comp.unix.wizards
- Path: sparky!uunet!cs.utexas.edu!torn!utzoo!censor!comspec!scocan!larryp
- From: larryp@sco.COM (Larry Philps)
- Subject: Re: LACHMAN TCP/IP - SCO - where's the stream?
- Organization: SCO Canada, Inc.
- Distribution: usa
- Date: Sat, 15 Aug 1992 14:22:30 GMT
- Message-ID: <1992Aug15.142230.26436@sco.COM>
- References: <1992Aug12.005402.10349@tigger.jvnc.net>
- Sender: news@sco.COM (News administration)
- Lines: 33
-
- In <1992Aug12.005402.10349@tigger.jvnc.net> mtcusa@tigger.jvnc.net (Multilingual Technogies Corporation) writes:
-
- > HI:
- >
- > LACHMAN TCP/IP for SCO appears to be streams based. At least some of it.
- > What I need to know is where I could push a module.
- >
- > Here's my confusion:
- >
- > 1. I use 'telnet' to call a remote.
- > 2. After getting a shell prompt, I issue a streams I_LOOK call on fd 0.
- > 3. The call returns complaining that it is not a streams device.
-
- SCO TCP/IP is indeed implemented as a set of streams modules and
- drivers. However, also included with the system is a normal character
- device driver that implements the BSD socket interface. The existence
- of this driver allows BSD socket based applications to be ported
- easily. Telnet just happens to be such an application.
-
- If you really want to "push" a module onto an open stream, you will
- have to write your own application to use the AT&T TLI calls (such
- as t_open and t_connect) on the device /dev/inet/tcp. This will give
- you a true streams based tcp connection, onto which you can push any
- module that you like.
-
- ---
- #include <std/disclaimer>
-
- Larry Philps, SCO Canada, Inc.
- Postman: 130 Bloor St. West, 10th floor, Toronto, Ontario. M5S 1N5
- InterNet: larryp@sco.COM
- UUCP: {uunet,utcsri,sco}!scocan!larryp
- Phone: (416) 922-1937
-