From: byron@netapp.com (Byron Rakitzis)
To: rc@hawkwind.utcs.toronto.edu
Subject: informal survey regarding <{}
Date: Sun, 21 Mar 1993 22:12:26 -0500 [thread overview]
Message-ID: <9303220312.AA12650@netapp.netapp.com> (raw)
I was wondering if anyone in rc-land is using the <{} feature
with fifos.
Specifically, I've been thinking about ditching fifos in favor
of synchronous operation with tmp files.
Advantages:
o You can seek on a tmp file, so diff will work.
o tmp files are much closer in semantics to real pipes,
so I expect fewer bugs.
o fifos aren't present everywhere, files are.
o fifos don't work everywhere (e.g., the notorious
tmpfs bug), files do.
Disadvantages:
o Existing users might depend on fifos.
o Advantage of pipe in the kernel is lost; command must
wait on all the tmp files being written first.
I could even argue, based on the first item in "Advantages",
that one might want to use tmp files even over /dev/fd, but
I don't want to risk starting a flame war.
Anyway, reply to me and I can summarize to the list.
next reply other threads:[~1993-03-22 3:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1993-03-22 3:12 Byron Rakitzis [this message]
1993-03-22 3:32 ` Scott Merrilees
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=9303220312.AA12650@netapp.netapp.com \
--to=byron@netapp.com \
--cc=rc@hawkwind.utcs.toronto.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).