From: Charles Forsyth <charles.forsyth@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Spectre and Meltdown
Date: Wed, 10 Jan 2018 22:48:40 +0000 [thread overview]
Message-ID: <CAOw7k5iRB++oVdYaxUV68+GGRVajRPkTN=nLFLOMV5ce4KfXwg@mail.gmail.com> (raw)
In-Reply-To: <188F69327A86275BA90105F31906A720@felloff.net>
[-- Attachment #1: Type: text/plain, Size: 1224 bytes --]
If Intel sells you lemons, make lemonade (ok, ok, at least a whiskey sour).
I myself welcome our new speculative overlords, and look forward to new
interesting predictions, and perhaps even a renewed interest in
single-address space systems, since that's what we've got.
On 10 January 2018 at 21:43, <cinap_lenrek@felloff.net> wrote:
> > all binaries on any repo (9p.io, 9front.org, bell-labs.com) are taken on
> > faith to be safe; but it applies there too.
> > does anyone read all the various rc scripts carefully?
>
> how's that comparable? the broken promise is that web
> code will be contained in the browser tab so nobody needs
> to trust that code. and we can just run it. that assumption
> is proven over and over again to not be true due to bugs
> in the interpreter and bugs in the massive libraries exposed
> to it and now theres a case where its broken even if there is
> no obvious flaw in the interpreter.
>
> nobody promised, or tried to do that with a plan9 process.
>
> code running in plan9 can do whatever you can do. and
> easily crash the whole system. so you obviouly need to
> be cautous about what you run.
>
> and yes, you should read the code.
>
> --
> cinap
>
>
[-- Attachment #2: Type: text/html, Size: 1812 bytes --]
next prev parent reply other threads:[~2018-01-10 22:48 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-10 21:43 cinap_lenrek
2018-01-10 22:46 ` Skip Tavakkolian
2018-01-10 22:48 ` Charles Forsyth [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-01-15 11:26 cinap_lenrek
2018-01-10 20:30 cinap_lenrek
2018-01-10 20:41 ` Erik Quanstrom
2018-01-10 20:48 ` Skip Tavakkolian
2018-01-10 16:59 cinap_lenrek
2018-01-10 19:32 ` Skip Tavakkolian
2018-01-10 19:41 ` Erik Quanstrom
2018-01-10 20:52 ` Skip Tavakkolian
2018-01-10 20:56 ` Erik Quanstrom
2018-01-10 21:30 ` Skip Tavakkolian
2018-01-10 23:46 ` Richard Miller
2018-01-11 0:33 ` Bakul Shah
2018-01-11 0:55 ` Skip Tavakkolian
2018-01-11 9:35 ` hiro
2018-01-11 9:49 ` Rui Carmo
2018-01-11 9:58 ` Richard Miller
2018-01-12 11:45 ` hiro
2018-01-16 0:51 ` Jules Merit
2018-01-16 1:16 ` Jules Merit
2018-01-15 9:57 ` Giacomo Tesio
[not found] <1911496352.319586.1515073776091.ref@mail.yahoo.com>
2018-01-04 13:49 ` G B
[not found] ` <CAJSxfmJ18xgD1thWvT80=o321-qKCEfecYb37gaFyC=CApWvmg@mail.gmail.com>
[not found] ` <CAJSxfmKsqOZVpcGmqEK3ar=h0-z8qn0GvYy_JNH_8x2OztMXrw@mail.gmail.com>
2018-01-10 16:27 ` Skip Tavakkolian
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='CAOw7k5iRB++oVdYaxUV68+GGRVajRPkTN=nLFLOMV5ce4KfXwg@mail.gmail.com' \
--to=charles.forsyth@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).