9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Jun OKAJIMA <okajima.digitalinfra@gmail.com>
To: 9fans@9fans.net
Subject: [9fans] Per Application Name Space
Date: Wed,  2 Dec 2009 02:13:17 +0900	[thread overview]
Message-ID: <f7b02ebf0912010913u58d856idc6fcace7be26fa4@mail.gmail.com> (raw)

Hello 9Fans readers.

First, please try my "Secure Click".
http://www.secureclick.jp/

Secure Click is a new secure application
executing environment.
Secure Click can run *any* distribution *safely* under jail.

Anyway, try it out first.

The core of Secure Click consists of two parts:
1. Jail.    OpenVZ and LXC is supported for now.
2. Per Application Name Space.


Secure Click runs apps by "One App in One Jail" basis.
So, each app is isolated from both other apps and host OS.

And, each jail has own file tree, synthesized by "tagfs".
"tagfs" synthesizes file tree which is very same for
each distribution.
I mean, for example, when you run debian app in jail,
tagfs creates debian file tree, which is very same for
real debian. If you run Fedora app, tagfs creates
Fedora tree.
So, you can run any distribution under jail.

In the other aspect of view, each app has each name space
which is derived from each distribution.
I think this is a kind of "Per *Application* Name Space".
And this is similar to Plan9 "Per User" name space concept,
so this is the reason I want to hear opinions from Plan9
experts like you.

Any impression is very welcome.

By the way, anybody knows where to discuss
*general* technological aspect of linux distribution?
There are many MLs for each distribution,
but no general one.


   --- Okajima, Jun. Tokyo, Japan.
        http://www.digitalinfra.co.jp/
        http://www.secureclick.jp/



             reply	other threads:[~2009-12-01 17:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-01 17:13 Jun OKAJIMA [this message]
2009-12-02  3:18 ` Sam Watkins
2009-12-05  4:06   ` Jun OKAJIMA
2009-12-05  4:21     ` Sam Watkins

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=f7b02ebf0912010913u58d856idc6fcace7be26fa4@mail.gmail.com \
    --to=okajima.digitalinfra@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).