9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Jonas Amoson <jonas.amoson@home.se>
To: 9fans@9fans.net
Subject: [9fans] To virtualise cpu/fs/auth-servers, or not?
Date: Thu, 16 Apr 2009 22:06:01 +0200	[thread overview]
Message-ID: <49E78FA9.7080206@home.se> (raw)

The plan9-way seems to be to divide the tasks
of running programs, storing files, authenti-
cation and user interaction, to separate
servers or computers. This makes sense in
a large system with many users, but does it
also have appeal in a system with at most a
couple of users (mostly me)?

How do you feel about using virtualisation
(e.g. using vmware) for splitting the plan9-
roles to different virtual machines?

One take is that it is the task of the OS
to handle different task securely and in
isolation, but that it might be good to add
layers, for the sake of robustness?

Up till now, I have been drawterming to
an all-in-one cpu/fs/auth-server. Nothing
very demanding, really. More out for a
philosophical discussion.

Jonas Amoson



             reply	other threads:[~2009-04-16 20:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-16 20:06 Jonas Amoson [this message]
2009-04-16 20:30 ` erik quanstrom
2009-04-16 23:04   ` andrey mirtchovski
2009-04-17  2:33     ` erik quanstrom
2009-04-17  2:49       ` andrey mirtchovski

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=49E78FA9.7080206@home.se \
    --to=jonas.amoson@home.se \
    --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).