From: Luciano Miguel Ferreira Rocha <luciano@lsd.di.uminho.pt>
To: linux-kernel@vger.kernel.org
Subject: Re: SVR4 STREAMS (for example LiS)
Date: Mon, 21 Jul 2003 15:50:42 +0100 [thread overview]
Message-ID: <20030721145042.GA17555@lsd.di.uminho.pt> (raw)
In-Reply-To: <Pine.LNX.4.53.0307211031460.18968@chaos>
On Mon, Jul 21, 2003 at 10:38:38AM -0400, Richard B. Johnson wrote:
> Streams are an extension of buffered I/O implimented by the 'C'
> runtime library. Streams really have nothing to do with the
> internal workings of kernel I/O. As far as kernel I/O goes,
> one reads() and writes() from user-space.
Actually, SysV Streams do.
An ex, for openning a pty, on svr4:
fds = open(pts_name, O_RDWR)
ioctl(fds, I_PUSH, "ptem")
ioctl(fds, I_PUSH, "ldterm")
ioctl(fds, I_PUSH, "ttcompat")
Where ptem, ldterm, ttcompat work as independent modules converting the
stream, resulting in a pseudo-terminal implementation.
New programs should just use openpty directly, and let libc take care
of the actual implementation.
Also, BSD sockets were implemented using streams also, thus the compatibility
libraries.
Anyway, I see no point in caring wether streams are used or not in normal
programs.
Regards,
Luciano Rocha
next prev parent reply other threads:[~2003-07-21 14:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-21 14:13 SVR4 STREAMS (for example LiS) Ihar "Philips" Filipau
2003-07-21 14:38 ` Richard B. Johnson
2003-07-21 14:50 ` Luciano Miguel Ferreira Rocha [this message]
[not found] <bJGh.25l.15@gated-at.bofh.it>
[not found] ` <bJZH.2jj.29@gated-at.bofh.it>
[not found] ` <bKj0.2yr.3@gated-at.bofh.it>
2003-07-22 7:24 ` Ihar "Philips" Filipau
2003-07-22 8:29 ` Bernd Eckenfels
[not found] <bZLc.6Xx.19@gated-at.bofh.it>
[not found] ` <bZLc.6Xx.21@gated-at.bofh.it>
[not found] ` <bZLc.6Xx.23@gated-at.bofh.it>
[not found] ` <bZLc.6Xx.17@gated-at.bofh.it>
2003-07-22 12:44 ` Ihar "Philips" Filipau
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030721145042.GA17555@lsd.di.uminho.pt \
--to=luciano@lsd.di.uminho.pt \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).