From: erik quanstrom <quanstro@coraid.com>
To: 9fans@9fans.net
Subject: Re: [9fans] To virtualise cpu/fs/auth-servers, or not?
Date: Thu, 16 Apr 2009 22:33:33 -0400 [thread overview]
Message-ID: <f328a58b35da7672cd4cf698db974c9d@coraid.com> (raw)
In-Reply-To: <14ec7b180904161604s1588b5b8k91c5740aefd18f7@mail.gmail.com>
On Thu Apr 16 19:08:23 EDT 2009, mirtchovski@gmail.com wrote:
> i still like to think of private namespaces as the ultimate
> virtualizer: your ns is your "virtual environment", the file server
> you're mounting is the "hypervisor". i don't care that it doesn't
> simulate actual hardware like xen/qemu. after all, each has layers and
> layers of abstractions to get you from the hardware to a usable
> environment.
it breaks down when you realize that some resources (processes, memory)
are not part of a namespace.
- erik
next prev parent reply other threads:[~2009-04-17 2:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-16 20:06 Jonas Amoson
2009-04-16 20:30 ` erik quanstrom
2009-04-16 23:04 ` andrey mirtchovski
2009-04-17 2:33 ` erik quanstrom [this message]
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=f328a58b35da7672cd4cf698db974c9d@coraid.com \
--to=quanstro@coraid.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).