From: "Mark K. Gardner" <mkgardne@cs.uiuc.edu>
To: rc@hawkwind.utcs.toronto.edu
Subject: Re: named pipe support (Was: autoconfig)
Date: Wed, 2 Apr 1997 09:37:43 -0500 [thread overview]
Message-ID: <199704021437.IAA28138@pertsserver.cs.uiuc.edu> (raw)
[ On Tue, April 1, 1997 at 14:28:39 (-0500), Byron Rakitzis wrote: ]
> I am sorely tempted to remove named pipe support. It never worked
> properly. So something is needed to auto-sense the particular
> encoding for /dev/fd (systems encode this differently), which I
> doubt is supplied by GNU autoconf.
I must confess that as a new user of RC, I have not made use of the
named pipe feature. However, I have needed such a feature for a long
time. (Now that I know it is there I will definitely try it out.) I
would like to add my support for continuing the feature and fixing the
problems. Which brings up my next question. What are the problems with
named pipes as they are currently implemented?
--
Mark K. Gardner (mkgardne@cs.uiuc.edu)
University of Illinois at Urbana-Champaign
Real-Time Systems Laboratory
--
reply other threads:[~1997-04-02 23:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=199704021437.IAA28138@pertsserver.cs.uiuc.edu \
--to=mkgardne@cs.uiuc.edu \
--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).