From: clemc@ccc.com (Clem cole)
Subject: [TUHS] Unix v6 problem with /tmp
Date: Wed, 27 Jul 2016 20:49:27 -0400 [thread overview]
Message-ID: <9A62D3AA-2905-44A6-B9F1-73644935AA70@ccc.com> (raw)
In-Reply-To: <5799234F.80108@gmail.com>
Yep. We used it for both but discovered it tended to be better for our system as a /tmp because we tried really hard to keep the 11/70 from swapping in those days.
Clem
Sent from my PDP-7 Running UNIX V0 expect things to be almost but not quite.
> On Jul 27, 2016, at 5:10 PM, William Pechter <pechter at gmail.com> wrote:
>
> Clem Cole wrote:
>> That is exactly how its was done. In fact, DEC made a Solid State Disk (out of RAM) just for UNIX that people used to use for /tmp.
> Are you referring to the slick little ML11-A (I think it was an -A when I installed it at NY Telephone on
> West Street, next to the World Trade Center...
>
> I seem to remember it being used as an RS04 (or similar) fixed head disk replacement for swap -- but
> it could've been used for temp.
>
> Funny seeing a fault light on a Massbus controller'd box of mostly MK11 memory.
> IIRC it had write-lock as well.
>
> Neat idea and I wish someone would come up with a really large SSD with a writelock for archival storage
> of my stuff. No head crashes and if I could disable the possibility of accidental writing...
>
> Bill
>
> --
> Digital had it then. Don't you wish you could buy it now!
> pechter-at-gmail.com http://xkcd.com/705/
>
next prev parent reply other threads:[~2016-07-28 0:49 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2016-07-28 1:03 ` William Pechter
2016-07-28 11:23 ` [TUHS] History repeating itself (was: Unix v6 problem with /tmp) Michael Kjörling
2016-07-28 12:18 ` Tony Finch
2016-07-28 13:57 ` John Cowan
2016-07-30 7:56 ` Greg 'groggy' Lehey
2016-07-30 11:41 ` William Cheswick
2016-07-30 23:28 ` Greg 'groggy' Lehey
2016-07-30 23:50 ` scj
2016-08-01 11:36 ` Tony Finch
2016-07-30 14:15 ` John Cowan
2016-07-30 15:30 ` [TUHS] History repeating itself Michael Kjörling
2016-07-28 1:03 ` [TUHS] Unix v6 problem with /tmp Clem cole
2016-07-28 23:16 ` [TUHS] environments/universes (was: Unix v6 problem with /tmp) Sven Mascheck
2016-07-29 3:05 ` arnold
2016-07-29 14:14 ` Clem Cole
2016-07-29 13:55 ` Clem Cole
2016-07-27 20:41 [TUHS] Unix v6 problem with /tmp Norman Wilson
2016-07-27 21:18 Norman Wilson
2016-07-28 0:47 ` 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=9A62D3AA-2905-44A6-B9F1-73644935AA70@ccc.com \
--to=clemc@ccc.com \
/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).