STREAMS(4) BSD/i386 Kernel Interfaces Manual STREAMS(4)NAME
streams -- System V STREAMS networking ABI support
SYNOPSIS
To compile support for this ABI into the kernel, place the following line in your kernel configuration file:
device streams
Alternatively, to load the ABI as a module at boot time, place the following line in loader.conf(5):
streams_load="YES"
DESCRIPTION
The streams module provides limited System V Release 4 STREAMS interprocess communication ABI (application binary interface) compatibility
for userland applications.
Internally, streams provides STREAMS handles by using socket creation kernel routines, and adding state-tracking information to the socket to
permit manipulation by STREAMS emulation code in svr4(4). Hence, opening a stream device produces a result similar to what would be obtained
by calling socket(2).
Applications should never use this interface directly: STREAMS emulation is only provided as a service to support ABI requirements in the
SVR4 environment which svr4(4) needs to present to client binaries.
SEE ALSO svr4(4)HISTORY
System V Release 4 ABI support first appeared in FreeBSD 4.0. The ABI was ported from an equivalent facility present in NetBSD 1.3 written
by Christos Zoulas.
BUGS
This whole interface is a crude hack to produce STREAMS semantics through emulation over sockets.
Programmers who hope to be able to use this interface to provide SVR4 STREAMS services to BSD applications will be sorely disappointed.
BSD March 17, 2008 BSD
Check Out this Related Man Page
STREAMS(4) BSD/i386 Kernel Interfaces Manual STREAMS(4)NAME
streams -- System V STREAMS networking ABI support
SYNOPSIS
To compile support for this ABI into the kernel, place the following line in your kernel configuration file:
device streams
Alternatively, to load the ABI as a module at boot time, place the following line in loader.conf(5):
streams_load="YES"
DESCRIPTION
The streams module provides limited System V Release 4 STREAMS interprocess communication ABI (application binary interface) compatibility
for userland applications.
Internally, streams provides STREAMS handles by using socket creation kernel routines, and adding state-tracking information to the socket to
permit manipulation by STREAMS emulation code in svr4(4). Hence, opening a stream device produces a result similar to what would be obtained
by calling socket(2).
Applications should never use this interface directly: STREAMS emulation is only provided as a service to support ABI requirements in the
SVR4 environment which svr4(4) needs to present to client binaries.
SEE ALSO svr4(4)HISTORY
System V Release 4 ABI support first appeared in FreeBSD 4.0. The ABI was ported from an equivalent facility present in NetBSD 1.3 written
by Christos Zoulas.
BUGS
This whole interface is a crude hack to produce STREAMS semantics through emulation over sockets.
Programmers who hope to be able to use this interface to provide SVR4 STREAMS services to BSD applications will be sorely disappointed.
BSD March 17, 2008 BSD
I need some help trying to access a 5250 emulation from an AS/400 from a unix box. I want to be able to be logged into the unix box and pull up a 5250 emulation screen from those terminals. Any Ideas on how to do this? (2 Replies)
Hi All,
while compiling on HP UX, i am getting the following error
ld: Can't find library or mismatched ABI for -lstlport_aCC
i am new to unix and HPUX, please suggest solution ASAS
thanks in advance
vindhyalesh (3 Replies)
Hi all,
I have a AIX kernel STREAMS question need your help,
I need to implement a firewall on AIX and get packet raw data then decide pass or drop it,
I've seen similiar firewall code on HP-UX,
on HP-UX, you have to implement a "dlpi STREAMS driver", and specify it as a "dlpi" driver in... (1 Reply)
Hello,
Long-time Unix hacker here - I've worked on four variants of the kernel prior to the introduction of Linux. In my spare time, I've written Linux (Ubuntu) device drivers, kernel modules, cross-compiled, and built the kernel.
I'd like to do Linux internals/device drivers as a day job,... (1 Reply)