9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Chris McGee <newton688@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Is Plan 9 C "Less Dangerous?"
Date: Thu,  6 Sep 2018 07:41:21 -0400	[thread overview]
Message-ID: <CAOk9ws0p8DoeiimVebaJY2yc6zeXe0kadb4Xom1btZ3t=DztCQ@mail.gmail.com> (raw)
In-Reply-To: <CAJQ9t7jbHhB0fhWU2nxWMg=kMKjYKGX2xwwP1T-M5bS3g441Rw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1370 bytes --]

> What one wants is Plan 9 as a
> model for what may be a family of hardware APIs. It makes sense to
> promote massive parallelism, but the API to it should be sufficiently
> simple for a single individual to manage.
>

This is the what I wonder about. Is this possible at the hardware level and
still support an equally simple, understandable, yet capable, software
system on top? By extension, would Plan 9 would run on such a system or if
it would require some fundamental changes to adapt to it. For example, does
C really need to be thrown out or can it be revised.


> Most computing devices today are single-user, even those like my new
> Android phone that offer shared user capabilities. Incidentally, the
> authorisation model in this case is inadequate for my purpose (share
> with a pre-teen).
>

I am in this boat too, however I have a general aversion to cloud computing
and so I would need some household multi-user systems for data storage and
heavy processing tasks or some distributed equivalent.


> So we have layers and we need the complexity to be shoved into
> well-tested, sealed boxes that can be trusted, while the surface
> remains as simple as 9P.
>

My trouble is that I don't trust the sealed boxes anymore after Meltdown,
Spectre, Rowhammer, etc. Perhaps simple and auditable hardware might help
with this.

[-- Attachment #2: Type: text/html, Size: 1886 bytes --]

  reply	other threads:[~2018-09-06 11:41 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-02 16:31 Chris McGee
2018-09-02 16:52 ` hiro
2018-09-03  4:07   ` Lucio De Re
2018-09-03 12:40     ` Chris McGee
2018-09-03 17:58       ` Ethan Gardener
2018-09-04 10:51         ` Lucio De Re
2018-09-04 11:33           ` Ethan Gardener
2018-09-04 11:41             ` Chris McGee
2018-09-02 18:16 ` Lucio De Re
2018-09-02 19:18   ` Steve Simon
2018-09-02 19:21 ` Iruatã Souza
2018-09-03  1:03   ` Charles Forsyth
2018-09-03  2:03 ` Skip Tavakkolian
2018-09-04 23:17 ` Charles Forsyth
2018-09-04 23:30   ` Tyga
2018-09-05  2:29     ` Chris McGee
2018-09-05 11:23       ` Dave MacFarlane
2018-09-05 11:42         ` Chris McGee
2018-09-05 13:35           ` Ethan Gardener
2018-09-05 15:38           ` Iruatã Souza
2018-09-05 23:59             ` Chris McGee
2018-09-06  0:32           ` Bakul Shah
2018-09-06  3:40             ` Lucio De Re
2018-09-06 11:41               ` Chris McGee [this message]
2018-09-06 13:37             ` Ethan Gardener
2018-09-06 17:48           ` Richard Miller
2018-09-06 19:08             ` Skip Tavakkolian
2018-09-06 21:21             ` Chris McGee
2018-09-07  8:32               ` Richard Miller
2018-09-05  3:25     ` Ori Bernstein
2018-09-05  8:19       ` Ethan Gardener

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='CAOk9ws0p8DoeiimVebaJY2yc6zeXe0kadb4Xom1btZ3t=DztCQ@mail.gmail.com' \
    --to=newton688@gmail.com \
    --cc=9fans@9fans.net \
    /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).