From: Dan Cross <cross@math.psu.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] \n\n\n to \n\n
Date: Mon, 3 Mar 2003 09:25:19 -0500 [thread overview]
Message-ID: <200303031425.h23EPJM22744@augusta.math.psu.edu> (raw)
In-Reply-To: Your message of "Mon, 03 Mar 2003 10:09:09 GMT." <3E5FE8D6.1080206@null.net>
> No, sam -d gets its commands from stdin, but you
> ought to be able to open from one stream and write
> to another, e.g. on Research Unix one could
> shuffle file descriptors in the Bourne shell (exec
> sometimes helped) and sam could read /dev/fd/4 and
> write /dev/fd/5 for example). A different form of
> plumbing.
Hmm, sounds a lot like /fd/*. rc(1) lets you shuttle file
descriptors around rather easily.
- Dan C.
next prev parent reply other threads:[~2003-03-03 14:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-28 18:48 Joel Salomon
2003-03-03 10:09 ` Douglas A. Gwyn
2003-03-03 14:25 ` Dan Cross [this message]
[not found] <1900322893@snellwilcox.com>
2003-03-03 11:14 ` Steve Simon
2003-03-04 10:26 ` Fco.J.Ballesteros
-- strict thread matches above, loose matches on Subject: below --
2003-02-28 12:42 peter a. cejchan
2003-02-28 18:11 ` Russ Cox
2003-03-03 10:08 ` Ralph Corderoy
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=200303031425.h23EPJM22744@augusta.math.psu.edu \
--to=cross@math.psu.edu \
--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).