diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2011-November/009737.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2011-November/009737.html | 130 |
1 files changed, 130 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-November/009737.html b/zarb-ml/mageia-dev/2011-November/009737.html new file mode 100644 index 000000000..026983bf0 --- /dev/null +++ b/zarb-ml/mageia-dev/2011-November/009737.html @@ -0,0 +1,130 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Drakx-net or NetworkManager for Mageia 2 + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Drakx-net%20or%20NetworkManager%20for%20Mageia%202&In-Reply-To=%3C4ECB9DCD.8080104%40roadrunner.com%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="009720.html"> + <LINK REL="Next" HREF="009699.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Drakx-net or NetworkManager for Mageia 2</H1> + <B>Frank Griffin</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Drakx-net%20or%20NetworkManager%20for%20Mageia%202&In-Reply-To=%3C4ECB9DCD.8080104%40roadrunner.com%3E" + TITLE="[Mageia-dev] Drakx-net or NetworkManager for Mageia 2">ftg at roadrunner.com + </A><BR> + <I>Tue Nov 22 14:04:13 CET 2011</I> + <P><UL> + <LI>Previous message: <A HREF="009720.html">[Mageia-dev] Drakx-net or NetworkManager for Mageia 2 +</A></li> + <LI>Next message: <A HREF="009699.html">[Mageia-dev] Drakx-net or NetworkManager for Mageia 2 +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#9737">[ date ]</a> + <a href="thread.html#9737">[ thread ]</a> + <a href="subject.html#9737">[ subject ]</a> + <a href="author.html#9737">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On 11/21/2011 10:38 PM, Balcaen John wrote: +><i> Le mardi 22 novembre 2011 00:11:49, Frank Griffin a écrit : +</I>><i> +</I>>><i> Please understand that I have *never* modified any Mageia-installed NM +</I>>><i> configuration file. +</I>><i> Ok so in fact you did not follow my suggestion here +</I>><i> <A HREF="https://bugs.mageia.org/show_bug.cgi?id=865#c1">https://bugs.mageia.org/show_bug.cgi?id=865#c1</A> ? +</I> +You know very well I did, as documented in +<A HREF="https://bugs.mageia.org/show_bug.cgi?id=865#c2">https://bugs.mageia.org/show_bug.cgi?id=865#c2</A> . + +To be more precise, the problem originally occurred with configuration +files as installed by Mageia, unmodified by me. I was simply making the +point that the problem scenario wasn't some custom arrangement that I +might have screwed up. + +><i> hum ? +</I>><i> The only comment here was that : +</I>><i> 1) ifcfg-mdv plugin was broken (& now in fact dead in mageia 2+) +</I>><i> +</I>><i> 2) try ifcfg-rh to see if it's also affected ( +</I>><i> <A HREF="https://bugs.mageia.org/show_bug.cgi?id=865#c6">https://bugs.mageia.org/show_bug.cgi?id=865#c6</A> ) +</I>><i> you did not try arguing that the maintainer should report it upstream. +</I>><i> ( <A HREF="https://bugs.mageia.org/show_bug.cgi?id=865#c8">https://bugs.mageia.org/show_bug.cgi?id=865#c8</A> ) which is quite difficult if +</I>><i> the maintainer (well in this case there is no maintainer so it's even more +</I>><i> difficult) is not able to reproduce simply because for example he does not have +</I>><i> the same wifi card. That's why i suggest you to report it upstream since you +</I>><i> should be able to answer questions from upstream if needed. +</I> +This entire discussion makes it evident why I wasn't the best one to +report it upstream. Far more about how NM was introduced into Mageia +has come out in this thread than was ever posted in the bugs I +mentioned. The googled references to other people having the problem +were not hardware-specific, and didn't involve the hardware I was using, +so the knowledge of whoever implemented NM in Mageia would be far more +valuable to upstream than access to my hardware. I posted detailed +logs, and I would have been following the upstream bug in any case. + + +><i> 3) keyfile is not affected by the hostname bug in #865 +</I>><i> +</I>><i> However when i suggested to switch to keyfile (on irc indeed not on mageia +</I>><i> mailing list) instead of the ifcfg-rh plugin or (any others non native +</I>><i> plugins) i was told that we need to support ifcfg (which is right indeed) +</I>><i> +</I>><i> So in summary we have a working plugin (keyfile) but we're not able to use it +</I>><i> because we need to support ifcfg- files so we're stick with the redhat plugin +</I>><i> for now until we found someone able to fix the missing functionnalities in this +</I>><i> plugin. +</I> +This really is not about saying you (or anyone else) did anything wrong +here. I'm just making the point that Cauldron shouldn't be a one-way +street. When something gets dropped in and has serious enough problems, +and the situation (for whatever reason) prevents us from being able to +fix it, then the appropriate thing to do is withdraw it until we can. +</PRE> + + + + + + + + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="009720.html">[Mageia-dev] Drakx-net or NetworkManager for Mageia 2 +</A></li> + <LI>Next message: <A HREF="009699.html">[Mageia-dev] Drakx-net or NetworkManager for Mageia 2 +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#9737">[ date ]</a> + <a href="thread.html#9737">[ thread ]</a> + <a href="subject.html#9737">[ subject ]</a> + <a href="author.html#9737">[ 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> |