From: norman@oclsc.org (Norman Wilson)
Subject: [TUHS] Unix v6 problem with /tmp
Date: Wed, 27 Jul 2016 16:41:05 -0400 [thread overview]
Message-ID: <1469652072.20272.for-standards-violators@oclsc.org> (raw)
William Pechter:
Only thing I can think of is add another drive or partition and mount it
as /tmp.
=====
You say that as if it's a bad thing.
Norman Wilson
Toronto ON
mount >> ln -s
next reply other threads:[~2016-07-27 20:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-27 20:41 Norman Wilson [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-07-27 21:18 Norman Wilson
2016-07-28 0:47 ` Clem cole
2016-07-27 20:28 Mark Longridge
2016-07-27 20:31 ` William Pechter
2016-07-27 20:57 ` Clem Cole
2016-07-27 21:01 ` Clem Cole
2016-07-27 21:10 ` William Pechter
2016-07-28 0:49 ` Clem cole
2016-07-28 1:03 ` William Pechter
2016-07-28 1:03 ` Clem cole
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=1469652072.20272.for-standards-violators@oclsc.org \
--to=norman@oclsc.org \
/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).