From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] tar.c, should use readn() instead of read().
Date: Mon, 12 Aug 2002 11:09:11 -0400 [thread overview]
Message-ID: <fc46bf318187bf624b3727087106a835@plan9.bell-labs.com> (raw)
> I'm not quite sure of the motivation between the difference. It
> seems a bit silly to me since its just buffering and doesn't have
> anything to do with semantics. Writing-to/reading-from raw tape
> drives (and newer media) does have size restrictions so I understand
> the feeling out of the read size. However, I'm not sure why
> the stdin/out should be limited to such a small buffer size, perhaps
> a throwback to limitations long gone.
Of course, on every other system, not specifying an f option
gets you /dev/tape rather than stdin/stdout, which just makes
it even weirder.
Russ
next reply other threads:[~2002-08-12 15:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-12 15:09 Russ Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-08-12 14:04 presotto
2002-08-13 9:31 ` Douglas A. Gwyn
2002-08-12 8:59 Aki M Nyrhinen
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=fc46bf318187bf624b3727087106a835@plan9.bell-labs.com \
--to=rsc@plan9.bell-labs.com \
--cc=9fans@cse.psu.edu \
/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).