9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Dave Eckhardt <davide+p9@cs.cmu.edu>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
Subject: Re: [9fans] directly opening Plan9 devices
Date: Thu,  8 Jan 2009 02:45:40 -0500	[thread overview]
Message-ID: <26462.1231400740@lunacy.ugrad.cs.cmu.edu> (raw)
In-Reply-To: <13426df10901070855t49869a03k3db4fb51b69373a3@mail.gmail.com>

> The underlying assumption of motivation for this discussion is that
> jailing (or whatever we want to call it) is somehow a good thing.
> Given that every CPU we care about comes with virtualization
> hardware, I just can't see the point of jails -- seems like an idea
> whose time has gone, kind of like 8086 segments.

I don't see how virtualization hardware solves "the applet problem",
or least privilege in general.  While you want un-trusted or
semi-trusted code to be walled off from *most* of your stuff, you want
it to access *some* of your stuff, such as part of your screen.  If
you run it on a virtual-other machine, you still need a way to specify
which of your stuff you want exported to that other machine.  Java has
a way of doing that, which is nice and complicated.  It seems as if
considering all resources to be files and sticking different subsets
of them into different namespaces might be less painful.

This isn't an emergency for anybody running Plan 9, nor, apparently,
anybody else, since most OS's are pretty coarse-grained about
privileges, but it might be worth thinking about.

Dave Eckhardt



  parent reply	other threads:[~2009-01-08  7:45 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-03 21:44 Roman V. Shaposhnik
2009-01-03 21:46 ` erik quanstrom
2009-01-03 21:56   ` Roman V. Shaposhnik
2009-01-03 22:03     ` erik quanstrom
2009-01-03 22:40       ` Roman V. Shaposhnik
2009-01-03 22:46         ` Francisco J Ballesteros
2009-01-03 22:56           ` erik quanstrom
2009-01-04  5:00             ` Roman V. Shaposhnik
2009-01-04  5:40               ` erik quanstrom
2009-01-04  4:58           ` Roman V. Shaposhnik
2009-01-03 22:57         ` erik quanstrom
2009-01-03 23:15           ` Russ Cox
2009-01-03 23:17             ` erik quanstrom
2009-01-04  5:07             ` Roman V. Shaposhnik
2009-01-04  5:05           ` Roman V. Shaposhnik
2009-01-03 22:21     ` Francisco J Ballesteros
2009-01-03 22:40       ` erik quanstrom
2009-01-04  5:12       ` Roman V. Shaposhnik
2009-01-04  5:27         ` erik quanstrom
2009-01-04  5:39           ` lucio
2009-01-04  5:42             ` erik quanstrom
2009-01-05  0:52           ` Roman V. Shaposhnik
2009-01-05  6:21             ` Roman Zhukov
2009-01-05 11:00             ` Charles Forsyth
2009-01-06  5:02               ` Roman Shaposhnik
2009-01-06 14:17                 ` erik quanstrom
2009-01-07 16:55                   ` ron minnich
2009-01-07 17:16                     ` erik quanstrom
2009-01-08  5:13                       ` ron minnich
2009-01-08 13:37                         ` erik quanstrom
2009-01-08 14:03                           ` Charles Forsyth
2009-01-08 15:36                           ` ron minnich
2009-01-08 15:44                             ` erik quanstrom
2009-01-08 17:34                             ` Roman V. Shaposhnik
2009-01-08 17:35                             ` Charles Forsyth
2009-01-08  7:45                     ` Dave Eckhardt [this message]
2009-01-08 17:43                     ` Roman V. Shaposhnik
2009-01-08 23:30                   ` Roman V. Shaposhnik
2009-01-04  7:01         ` Russ Cox
2009-01-04 11:41           ` lucio
2009-01-04 13:01             ` Uriel
2009-01-04 13:16               ` lucio
2009-01-05  0:41           ` Roman V. Shaposhnik

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=26462.1231400740@lunacy.ugrad.cs.cmu.edu \
    --to=davide+p9@cs.cmu.edu \
    --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).