rc-list - mailing list for the rc(1) shell
 help / color / mirror / Atom feed
From: Scott Merrilees <Sm@cerberus.bhpese.oz.au>
To: byron@netapp.com (Byron Rakitzis)
Cc: rc@hawkwind.utcs.toronto.edu
Subject: Re: informal survey regarding <{}
Date: Sun, 21 Mar 1993 22:32:21 -0500	[thread overview]
Message-ID: <199303220332.AA10340@cerberus.bhpese.oz.au> (raw)
In-Reply-To: Your message of "Sun, 21 Mar 93 22:12:26 EST." <9303220312.AA12650@netapp.netapp.com>


>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.

I'd be interested in the tmp file approach.  Fifos don't work under
risc/os 4.52.  I tried to write a /dev/fd file system for the kernel,
but am getting some kernel crashes because of undocumented
interfaces.

Is there anything wrong with having tmp files as the default, and
fifos & /dev/fd as options ?

Sm


      reply	other threads:[~1993-03-22  3:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1993-03-22  3:12 Byron Rakitzis
1993-03-22  3:32 ` Scott Merrilees [this message]

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=199303220332.AA10340@cerberus.bhpese.oz.au \
    --to=sm@cerberus.bhpese.oz.au \
    --cc=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).