From: aq <aquynh@gmail.com>
To: Ray Valdez <rvaldez@us.ibm.com>
Cc: xen-devel@lists.xensource.com, Stefan Berger <stefanb@us.ibm.com>,
Leendert Van Doorn <leendert@us.ibm.com>,
Reiner Sailer <sailer@us.ibm.com>,
Tupshin Harper <tupshin@tupshin.com>,
Reiner Sailer <sailer@watson.ibm.com>,
Ronald Perez <ronpz@us.ibm.com>,
steven.hand@cl.cam.ac.uk, xense-devel@lists.xensource.com
Subject: Re: [PATCH] sHype access control architecture for Xen
Date: Tue, 21 Jun 2005 23:48:33 +0900 [thread overview]
Message-ID: <9cde8bff0506210748541bf38b@mail.gmail.com> (raw)
In-Reply-To: <OF5376BAE3.29533A79-ON85257027.004B2311-85257027.004BF071@us.ibm.com>
On 6/21/05, Ray Valdez <rvaldez@us.ibm.com> wrote:
> On 6/21/05, Tupshin Harper <tupshin@tupshin.com> wrote:
> > aq wrote:
> >
> > >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.
> > >
> > >since python is used in xen, i think it is a good candidate.
> > >
> > >i will play with the code and give some feedbacks.
>
> > Ensuring that the code compiles cleanly with gcj would eliminate this
> issue.
>
> We will look into compiling the tool with gcj. Thanks. We will appreciate
> your feedback.
>
> > but we still need java to run the binary code, dont we?
>
> No. The tool is used for generating a binary policy file, which can then be
> loaded into sHype via the
> xeno-unstable.bk/tools/policy/policy_tool command.
>
to tell the truth, installing java into any of my machines is the last
thing i want to do. if it is possible to compile java code to native
binary, that would be great. then java turns out to be even better
than python, right ;-)
regards,
aq
next prev parent reply other threads:[~2005-06-21 14:48 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 [this message]
2005-06-21 12:32 ` Scott Parish
2005-06-21 13:25 ` Alvin Starr
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=9cde8bff0506210748541bf38b@mail.gmail.com \
--to=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=tupshin@tupshin.com \
--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.