From: Alvin Starr <alvin@iplink.net>
To: aq <aquynh@gmail.com>
Cc: xen-devel@lists.xensource.com, ronpz@us.ibm.com,
leendert@us.ibm.com, rvaldez@us.ibm.com, sailer@us.ibm.com,
xense-devel@lists.xensource.com,
Reiner Sailer <sailer@watson.ibm.com>,
stefanb@us.ibm.com, steven.hand@cl.cam.ac.uk
Subject: Re: [PATCH] sHype access control architecture for Xen
Date: Tue, 21 Jun 2005 09:25:32 -0400 [thread overview]
Message-ID: <42B8154C.2050301@Iplink.net> (raw)
In-Reply-To: <9cde8bff05062022475468b1c9@mail.gmail.com>
aq wrote:
>On 6/21/05, Reiner Sailer <sailer@watson.ibm.com> wrote:
>
>
>>This E-mail contains the sHype access control architecture
>>for inclusion into the Xen hypervisor (xeno-unstable.bk).
>>This is a follow-up on earlier postings:
>>http://lists.xensource.com/archives/html/xen-devel/2005-04/msg00864.html
>>
>>
>>
[snip]
>any plan to write the tool in other language, not Java? i guess not
>many people (include me) are willing to install Java on their system.
>
Hmmm. I have the same complaint about Python. I tend to like anything
that can be compiled into a more or less standalone binary.
The current Python tools have a whole chain of dependancies and I often
find that this kind of thing ends up leaving me in a situation where I
have conflicting dependancies.
I just love staicaly compiled binaries or somthing that at most requires
the libraries you get with a stock libc install.
I have not looked at the sHype tools but it may be that they can be
compiled with gcj and turned into a static binary.
>
>since python is used in xen, i think it is a good candidate.
>
>i will play with the code and give some feedbacks.
>
>regards,
>aq
>
>_______________________________________________
>Xen-devel mailing list
>Xen-devel@lists.xensource.com
>http://lists.xensource.com/xen-devel
>
>
--
Alvin Starr || voice: (416)585-9971
Interlink Connectivity || fax: (416)585-9974
alvin@iplink.net ||
prev parent reply other threads:[~2005-06-21 13:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-20 17:22 [PATCH] sHype access control architecture for Xen Reiner Sailer
2005-06-21 5:47 ` aq
2005-06-21 6:26 ` Tupshin Harper
2005-06-21 7:35 ` aq
2005-06-21 10:56 ` Tupshin Harper
2005-06-21 11:26 ` Mark Williamson
2005-06-21 12:11 ` Grzegorz Milos
2005-06-21 13:49 ` Ray Valdez
2005-06-21 14:48 ` aq
2005-06-21 12:32 ` Scott Parish
2005-06-21 13:25 ` Alvin Starr [this message]
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=42B8154C.2050301@Iplink.net \
--to=alvin@iplink.net \
--cc=aquynh@gmail.com \
--cc=leendert@us.ibm.com \
--cc=ronpz@us.ibm.com \
--cc=rvaldez@us.ibm.com \
--cc=sailer@us.ibm.com \
--cc=sailer@watson.ibm.com \
--cc=stefanb@us.ibm.com \
--cc=steven.hand@cl.cam.ac.uk \
--cc=xen-devel@lists.xensource.com \
--cc=xense-devel@lists.xensource.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.