The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: rmswierczek@gmail.com (Robert Swierczek)
Subject: [TUHS] Questions for TUHS great minds
Date: Tue, 10 Jan 2017 21:33:03 -0500	[thread overview]
Message-ID: <CAAFR5pZBZWFLLR03+xHZng-wfJHvNxqX7WP6p=tuM4rMxmhfaw@mail.gmail.com> (raw)

Not so long ago I joked about putting a Cray-1 in a watch.  Now that we are
essentially living in the future, what audacious (but realistic)
architectures can we imagine under our desks in 25 years?  Perhaps a mesh
of ten-million of today's highest end CPU/GPU pairs bathing in a vast sea
of non-volatile memory?  What new abstractions are needed in the OS to
handle that?  Obviously many of the current command line tools would need
rethinking (ps -ef for instance.)

Or does the idea of a single OS disintegrate into a fractal cloud of
zero-cost VM's?  What would a meta-OS need to manage that?  Would we still
recognize it as a Unix?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170110/e4f419ed/attachment.html>


             reply	other threads:[~2017-01-11  2:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-11  2:33 Robert Swierczek [this message]
2017-01-11 16:25 ` Ron Natalie
2017-01-11 16:50   ` Jacob Goense
2017-01-11 17:01     ` Corey Lindsly
2017-01-11 17:54       ` Marc Rochkind
2017-01-11 20:32       ` Jacob Goense
2017-01-11 18:34 ` Steve Johnson
2017-01-11 19:46   ` Steffen Nurpmeso
2017-01-17 13:09   ` Tim Bradshaw
2017-01-17 13:36     ` Michael Kjörling
2017-01-17 19:55     ` Steve Johnson
2017-02-01 23:32       ` Erik E. Fair
2017-01-17 14:27 Nelson H. F. Beebe

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='CAAFR5pZBZWFLLR03+xHZng-wfJHvNxqX7WP6p=tuM4rMxmhfaw@mail.gmail.com' \
    --to=rmswierczek@gmail.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).