Avi Kivity wrote:
Jorge Lucángeli Obes wrote:
My feeling is that config files are outdated. When used with a gui,
you end up writing silly parsers and stuff and still wrecking things
horribly when the the gui writer's expectations don't match reality.
When used without a gui, they increase
On 8/13/07, Laurent Vivier [EMAIL PROTECTED] wrote:
I know we are not in democracy, but if I can vote I'd like to vote to the idea
of Christian Brunschen...
We can modify qemu to test if the argument is a directory, if yes, it reads
args
from file args in this directory and for security the
On 8/13/07, Daniel P. Berrange [EMAIL PROTECTED] wrote:
On Mon, Aug 13, 2007 at 11:04:46AM +0300, Avi Kivity wrote:
Luca Tettamanti wrote:
Something like:
- try to use HPET (unless -no-rtc selected)
- try to use RTC (unless -no-rtc selected)
- fallback to normal unix facilities
If
If readline_handle_byte() is sent both a CR and LF, and
readline_start() is not called after the first CR, then the LF will
cause the same command to be executed a second time. Fix this by
explicitly resetting the buffer pointers when it is processed.
Signed-off-by: Jim Paris [EMAIL PROTECTED]
This patch extends the QEMU monitor 'change' command so that it can
be used to change the configuration of the VNC server. On the command
line the user can use -vnc none, and then issue the 'change vnc :1'
command later from the monitor. This is utilized in the next patch
to let the monitor fetch
This patch introduces support for VNC protocols upto 3.8 and with
it, support for password based authentication. VNC's password based
authentication is not entirely secure, but it is a standard and the
RFB spec requires that all clients support it. The password can be
provided by using the monitor
This patch introduces minimal support for the VeNCrypt protocol
extension. This layers use of TLS (aka SSL) into the VNC data stream,
providing session encryption. This patch is the bare minimum protocol
support. It is enabled by using the 'tls' option flag eg -vnc :1,tls'
This is not secure on
This patch adds support for using x509 certificates on the server
end. The server needs a CA certificate, and its own certificate and
private key. A CA revocation list is optional. This this patch the
file names are hardcoded. The next-but-one patch will make them
configurable.
The use of x509
This final code patch extends the VNC server config syntax so that the x509
and x509verify flags both use a path following them. This path is then used
to determine the filenames for the CA certificate revocation list, and the
server certificate private key. If the path containing the
This patch updates the user documentation to detail the new syntax
options for VNC server configuration. It moves all the display
related options into a combined logical section for clarity. It
documents the different deployment secenarios possible with the
new VNC server capabilities and their
Jorge Lucángeli Obes wrote:
[snip]
When I read Avi's TODO, I basically thought about getting rid of the
long command lines I had to store in scripts. I wanted to write that
command line once, and then forgetting about it, until I needed to
change it.
Instead of inventing great and wonderfully
On 8/13/07, Thiemo Seufer [EMAIL PROTECTED] wrote:
Instead of inventing great and wonderfully complicated schemes, the
most sensible way I can think of is to recycle a feature which is now
implemented in the GNU toolchain, and apparently stems from Windows:
qemu @qemu.cfg
where qemu.cfg is
Il Mon, Aug 13, 2007 at 05:42:55PM +0300, Dan Kenigsberg ha scritto:
Dynamic ticks in Qemu: have a SIGALRM generated only when it is
needed, instead of every 1 millisecond. This patch requires that the
host supports high resolution timers, since it arms a POSIX timer to the
nearest Qemu
On 13 Aug 2007, at 20:39, Thiemo Seufer wrote:
Instead of inventing great and wonderfully complicated schemes, the
most sensible way I can think of is to recycle a feature which is now
implemented in the GNU toolchain, and apparently stems from Windows:
qemu @qemu.cfg
I'm not familiar with
On Tuesday, August 14, 2007, 0:21:42, Philip Boulain wrote:
qemu @qemu.cfg
I'm not familiar with that. Is it just GNU bash shorthand for qemu
`cat qemu.cfg` ?
GNU bash does not have that shorthand, but @file is very similar to
`cat file` (the practice was born in DOS days, because the
Hi,
when trying to write a driver that provides a ppdev-compatible API
but forwards the data written to the parport to a userspace program,
I noticed that Qemu (0.8.2-4etch1 from Debian Etch, but the changelog
of 0.9.0 doesn't look like it has been fixed there) doesn't handle
interrupted system
On 8/14/07, Anthony Liguori [EMAIL PROTECTED] wrote:
On Mon, 2007-08-13 at 20:39 +0100, Thiemo Seufer wrote:
Jorge Lucángeli Obes wrote:
[snip]
When I read Avi's TODO, I basically thought about getting rid of the
long command lines I had to store in scripts. I wanted to write that
17 matches
Mail list logo
