From: "Javier Guerra" <javier@guerrag.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: kvm-devel@lists.sourceforge.net, qemu-devel@nongnu.org
Subject: Re: [kvm-devel] [Qemu-devel] Re: [PATCH] Add support for a configuration file
Date: Wed, 14 May 2008 10:42:53 -0500 [thread overview]
Message-ID: <90eb1dc70805140842s2eff15cdp20bd0b29b1418e58@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.1.00.0805141634110.30431@racer>
On Wed, May 14, 2008 at 10:37 AM, Johannes Schindelin
<Johannes.Schindelin@gmx.de> wrote:
> On Wed, 14 May 2008, Javier Guerra wrote:
> > when embedded, you get to choose what libraries are available. there
> > are several examples of fairly secure settings.
>
> Why artificially make it complicated, and then have to take care of such
> issues?
i should have said "Lua is secure by default, all libraries are
optional", but it's quickly turning into a bikeshed
(http://www.bikeshed.com)
my own personal preference would be to just stuff the whole command
line parameters into the qcow2 image file.
--
Javier
next prev parent reply other threads:[~2008-05-14 15:42 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-13 21:19 [Qemu-devel] [PATCH] Add support for a configuration file Anthony Liguori
2008-05-13 23:07 ` [Qemu-devel] " Anthony Liguori
2008-05-13 23:20 ` [Qemu-devel] Re: [kvm-devel] " Daniel P. Berrange
2008-05-14 6:35 ` Colin Adams
2008-05-14 14:41 ` Avi Kivity
2008-05-14 14:52 ` Dor Laor
2008-05-14 15:02 ` Daniel P. Berrange
2008-05-14 15:18 ` [kvm-devel] [Qemu-devel] " Anthony Liguori
2008-05-14 14:59 ` [Qemu-devel] Re: [kvm-devel] " Anthony Liguori
2008-05-14 15:10 ` Andreas Färber
2008-05-15 14:50 ` Ian Jackson
2008-05-14 8:27 ` [Qemu-devel] " Fabrice Bellard
2008-05-14 10:31 ` Avi Kivity
2008-05-14 12:26 ` Fabrice Bellard
2008-05-14 13:31 ` [kvm-devel] " Daniel P. Berrange
2008-05-15 8:04 ` Avi Kivity
2008-05-15 11:52 ` Daniel P. Berrange
2008-05-15 12:04 ` Avi Kivity
2008-05-15 12:16 ` Andreas Färber
2008-05-15 12:20 ` Laurent Vivier
2008-05-14 14:06 ` Anthony Liguori
2008-05-14 14:26 ` Paul Brook
2008-05-14 14:45 ` [kvm-devel] " Javier Guerra
2008-05-14 15:13 ` Johannes Schindelin
2008-05-14 15:30 ` Javier Guerra
2008-05-14 15:37 ` Johannes Schindelin
2008-05-14 15:42 ` Javier Guerra [this message]
2008-05-14 16:07 ` Kelly French
2008-05-15 14:59 ` Paul Brook
2008-05-14 16:01 ` Andreas Färber
2008-05-14 16:21 ` Daniel P. Berrange
2008-05-14 16:37 ` Andreas Färber
2008-05-14 16:29 ` Fabrice Bellard
2008-05-17 21:49 ` Luca Barbato
2008-05-14 15:22 ` Daniel P. Berrange
2008-05-14 15:09 ` Anthony Liguori
2008-05-14 15:18 ` Paul Brook
2008-05-14 16:25 ` Fabrice Bellard
2008-05-14 14:36 ` andrzej zaborowski
2008-05-14 15:10 ` Johannes Schindelin
2008-05-15 14:58 ` Ian Jackson
2008-05-15 12:03 ` [Qemu-devel] " Erik de Castro Lopo
2008-05-15 12:36 ` andrzej zaborowski
2008-05-15 13:22 ` Daniel P. Berrange
2008-05-15 14:46 ` andrzej zaborowski
2008-05-15 15:05 ` Anthony Liguori
2008-05-15 15:26 ` Avi Kivity
2008-05-15 18:50 ` Anthony Liguori
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=90eb1dc70805140842s2eff15cdp20bd0b29b1418e58@mail.gmail.com \
--to=javier@guerrag.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=kvm-devel@lists.sourceforge.net \
--cc=qemu-devel@nongnu.org \
/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).