diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2011-November/009574.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2011-November/009574.html | 162 |
1 files changed, 162 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-November/009574.html b/zarb-ml/mageia-dev/2011-November/009574.html new file mode 100644 index 000000000..e145d7ccd --- /dev/null +++ b/zarb-ml/mageia-dev/2011-November/009574.html @@ -0,0 +1,162 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] qemu new upstream release (1.0-rc1) and should we move from qemu-kvm to qemu? + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20qemu%20new%20upstream%20release%20%281.0-rc1%29%20and%20should%20we%0A%20move%20from%20qemu-kvm%20to%20qemu%3F&In-Reply-To=%3C4EC32EBC.5010102%40gmx.com%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="009524.html"> + <LINK REL="Next" HREF="009526.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] qemu new upstream release (1.0-rc1) and should we move from qemu-kvm to qemu?</H1> + <B>Kamil Rytarowski</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20qemu%20new%20upstream%20release%20%281.0-rc1%29%20and%20should%20we%0A%20move%20from%20qemu-kvm%20to%20qemu%3F&In-Reply-To=%3C4EC32EBC.5010102%40gmx.com%3E" + TITLE="[Mageia-dev] qemu new upstream release (1.0-rc1) and should we move from qemu-kvm to qemu?">n54 at gmx.com + </A><BR> + <I>Wed Nov 16 04:32:12 CET 2011</I> + <P><UL> + <LI>Previous message: <A HREF="009524.html">[Mageia-dev] qemu new upstream release (1.0-rc1) and should we move from qemu-kvm to qemu? +</A></li> + <LI>Next message: <A HREF="009526.html">[Mageia-dev] qemu new upstream release (1.0-rc1) and should we move from qemu-kvm to qemu? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#9574">[ date ]</a> + <a href="thread.html#9574">[ thread ]</a> + <a href="subject.html#9574">[ subject ]</a> + <a href="author.html#9574">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On 14.11.2011 14:53, Buchan Milne wrote: +><i> +</I>>>><i> ( and given the discussion +</I>>>><i> +</I>>>><i> on ml, it should be soon ) +</I>>><i> When I ask the developers, they don't know if qemu will include the +</I>>><i> patch at all and when (now or after one year) and they suggested to do +</I>>><i> the openSUSE way (today the most recommended and full featured Linux +</I>>><i> distro for GNS3). +</I>><i> [...] +</I>><i> +</I>>><i> OK. So if gns3 can't be fixed for the stable - than should be removed +</I>>><i> from the repos (for ISOs is to late). +</I>>><i> +</I>>><i> If we don't provide qemu patch, then gns3 should be removed from +</I>>><i> Cauldron as well. +</I>>><i> +</I>>><i> I believe removing GNS3 is better than keeping it broken and.. irritate +</I>>><i> people (I don't count the opinion of our quality). Later some 3rd party +</I>>><i> repos can provide GNS3 and its dependencies. +</I>><i> You seem to imply that the only use of GNS3 is with this qemu patch. +</I>It's possible to simulate and play without qemu. (btw newer alpha +release version supports in the same way VirtualBox) + +It should be "Suggested" by GNS3, but then what is the idea of +suggesting qemu that isn't working at all? I simply don't know why to +distribute a program that provides support in GUI for something that's +not working. + +People can try to waste their time and configure qemuwrapper with our +qemu... it's just a matter of time for a bugrequest on our bugzilla. + +In my opinion if we provide an application with so exposed (visible) +support for working with qemu and we don't provide qemu itself then our +quality of packages get lower. +><i> But I used GNS3 with just dynamips, and this issue of GNS3 not being +</I>><i> usable at +</I>><i> all due to missing dynamips can really be solved quite quickly just by +</I>><i> shipping dynamips to updates. +</I>Yes. +><i> But, it looks like someone blindly imported gns3 and dynagen from +</I>><i> Mandriva +</I>><i> without even understanding the use of these tools: +</I>><i> +</I>><i> $ rpm -q --suggests dynagen +</I>><i> dynamips>= 0.2.8 +</I>><i> xterm +</I>><i> +</I>><i> (dynamips isn't explicitly required to be installed on the host with +</I>><i> gns3 or +</I>><i> dynagen, as the hypervisor can be run on a different host than +</I>><i> dynagen/GNS3). +</I>><i> +</I>In theory yes. +><i> Regards, +</I>><i> Buchan +</I> +-------------- next part -------------- +An HTML attachment was scrubbed... +URL: </pipermail/mageia-dev/attachments/20111116/ebfb4023/attachment.html> +</PRE> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="009524.html">[Mageia-dev] qemu new upstream release (1.0-rc1) and should we move from qemu-kvm to qemu? +</A></li> + <LI>Next message: <A HREF="009526.html">[Mageia-dev] qemu new upstream release (1.0-rc1) and should we move from qemu-kvm to qemu? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#9574">[ date ]</a> + <a href="thread.html#9574">[ thread ]</a> + <a href="subject.html#9574">[ subject ]</a> + <a href="author.html#9574">[ author ]</a> + </LI> + </UL> + +<hr> +<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev +mailing list</a><br> +</body></html> |