From: bobf@research.att.com
To: sam-fans@hawkwind.utcs.toronto.edu
Date: Fri, 12 Mar 1993 15:26:58 -0500 [thread overview]
Message-ID: <93Mar12.153414est.2800@hawkwind.utcs.toronto.edu> (raw)
re: B command
in Boyd's original implmentation the pipe was in the home
directory, but i moved to /tmp to prevent network accesses
on the pipe and to have it automatically removed after a
system or program crash.
scott's observation confirms my experience: the location
of the named pipe is site-dependent. i'll update the README
file accordingly.
of course, in plan 9 we avoid the problem completely: by convention
the pipe is placed in a convenient place in the namespace.
reply other threads:[~1993-03-12 20:34 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=93Mar12.153414est.2800@hawkwind.utcs.toronto.edu \
--to=bobf@research.att.com \
--cc=sam-fans@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).