From: Scott Schwartz <schwartz@groucho.cs.psu.edu>
To: sam-fans@hawkwind.utcs.toronto.edu
Subject: tmpfs strikes again
Date: Fri, 12 Mar 1993 15:22:42 -0500 [thread overview]
Message-ID: <93Mar12.152322est.2539@groucho.cs.psu.edu> (raw)
In-Reply-To: Your message of "Fri, 12 Mar 1993 11:57:46 EST." <93Mar12.122143est.2793@hawkwind.utcs.toronto.edu>
The new pipe-to-sam feature is interesting. Unfortunately users of
Byron Rakitzis' rc (yay!) who also use SunOS tmpfs (boo!) will revisit
the old tmpfs-fifo problem: fifo's don't always work in tmpfs
(depending on open mode or something) and that's where sam puts one.
As a workaround, the changes in samterm/unix.c to put the fifo in
/usr/tmp instead are obvious.
prev parent reply other threads:[~1993-03-12 20:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1993-03-12 16:57 bobf
1993-03-12 20:22 ` Scott Schwartz [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=93Mar12.152322est.2539@groucho.cs.psu.edu \
--to=schwartz@groucho.cs.psu.edu \
--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).