The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: clemc@ccc.com (Clem cole)
Subject: [TUHS] Unix v6 problem with /tmp
Date: Wed, 27 Jul 2016 21:03:33 -0400	[thread overview]
Message-ID: <4316C91F-D35F-46D0-9AE8-955780BC5A32@ccc.com> (raw)
In-Reply-To: <5799234F.80108@gmail.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1066 bytes --]

Bill - below

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:
> 
> 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...

I had to laugh.   A few months back I was working with a very bright 20 something engineers (from one of my alma mater's ) who is working on our new Xpoint memory technology.   I had to explain to him some of these new behaviors / inventions were how things like core memory worked as well as showing him some info on the ML11 with exactly these type of features.   He had no idea.  

While I'm not part of the the Xpoint team I have no idea what will end up as exposed features in final product  or how people configure them but it's interesting to watch some ideas that stopping being fashionable or maybe economical be (re)discovered. 

What is new is old and old is now new😎

Clem


  parent reply	other threads:[~2016-07-28  1:03 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
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       ` Clem cole [this message]
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=4316C91F-D35F-46D0-9AE8-955780BC5A32@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).