I shouldn't write posts at 7-8am
should be
s/Certainly better every/Certainly better than every/
s/broken and compatible/broken and incompatible/
sry :) , you probably understood anyway what i meant ...
martin
martin wrote:
If we'd go for a config file at all with such a complicated struct
If we'd go for a config file at all with such a complicated structure, i see no reasons why to
choose anything else than xml for it. We have tons of xml libs that can be used for gui's (think
perl, tk, python etc...). Certainly better every dude writing it's own XuPeRpArSeR that will be
broken
On 1/3/06, Johannes Schindelin <[EMAIL PROTECTED]> wrote:
> > If I find 1 free hour tomorrow I'll post a POC.
>
> POC=Piece Of Crap??? ;-)
I can only hope he meant Proof Of Concept :)
--
"I decry the current tendency to seek patents on algorithms. There are
better ways to earn a living than to p
Hi,
On Tue, 3 Jan 2006, Flavio Visentin wrote:
> It would be useful for automatic startup of the VMs by init scripts.
> OTOH it's very simple to create a config file parser with
> perl/python/bash who can wrap around qemu options.
It is simpler to write the bash script right away, especially if
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Paul Brook wrote:
> Config file support without a decent GUI seem rather pointless.
> The big advantage of doing it as a shell script is it's dead easy to hack to
> include whatever custom magical features people want.
It would be useful for automati
> Result:
> - full compatibility with every version of qemu
> - more flexibility
> - possibility to set up the hardcode parameters
> - possibility of parameters personalized for every image
>
> One similar thing, with smaller flexibility, is possible
> without modify qemu and using one series of b
Hi.
My idea is this:
- qemu start
- set up of the hardcode parameters
- reading of the configuration file and set up of the parameters
- set up of the parameters of command line
Example of configuration file:
[general]
[vlan0]
ip= x.y.x.w
mac= l:m:n:o
[/vlan0]
[/
Hi Mulyadi,
The problem that you are running into here is that sys_uname has been
replaced by sys_newuname in kernel/sys.c. When I put a breakpoint in
this function, everything works correctly when I run uname in the
virtual machine.
I'm not sure I exactly understand your concern that breakpoints
Fabrice didn't know that this existed since recently. I had commented on
setting up bugzilla, but I found the savanna bts later.
I think it should stay open and start being used.
Currently everything is done over the mailinglist (some stuff via irc).
I think that should change.
- Mick
Adam
Hi,
Some changes to the ata/atapi identify code and default values:
- Store the drive id in the IDEState, so we can reliably set and query
new values. Right now doing things like:
# hdparm -Xudma2 /dev/hda
# hdparm -i /dev/hda (and check for mode)
doesn't work, as the IDENTIFY command will re
___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel
Hi,
>> Hmm, there seems to be a problem with your patch, though I haven't quite
>> figured out what exactly the cause is. When using the -busmouse option,
>> the busmouse_init function is called and seems to register the callbacks
>> for the provided I/O address ranges successfully (return value
On Tue, 3 Jan 2006, Johannes Schindelin wrote:
Hi,
On Tue, 3 Jan 2006, [EMAIL PROTECTED] wrote:
The most difficult problem was actually finding documentation on the
busmouse controller ;-).
That always seems to be the biggest problem...
How about this on top (unfortunately untested, since
Hi,
On Tue, 3 Jan 2006, [EMAIL PROTECTED] wrote:
> The most difficult problem was actually finding documentation on the
> busmouse controller ;-).
That always seems to be the biggest problem...
> > How about this on top (unfortunately untested, since I do not
> > have a system handy which supp
Hi,
> On Sun, 1 Jan 2006, [EMAIL PROTECTED] wrote:
>
>> I attached the correct version to this mail. Sorry...
>
> Impressive!
Thanks! The most difficult problem was actually finding documentation
on the busmouse controller ;-).
> How about this on top (unfortunately untested, since I do not
> h
15 matches
Mail list logo
