[Mageia-dev] Drakx-net or NetworkManager for Mageia 2

[John Balcaen]

2011/11/21 Frank Griffin <ftg at roadrunner.com>:
> On 11/21/2011 06:01 PM, Balcaen John wrote:
>>
>> Le lundi 21 novembre 2011 16:50:35 Frank Griffin a écrit :
>> [...]
>>>
>>> Sorry, I transposed - should have been 865.
>>
>> So here the problems here seems to happend when using the *specific* mdv
>> plugin
>> on mageia 1&  not with the native plugin (keyfile).
>
> Well, it uses whatever the Mageia install puts there.  I didn't change
> anything from the defaults, much less anything specific to NM, about which I
> know next to nothing.
I did not say anything else.
I personally don't use the rhplugin or the mdv before but always
switch to keyfile.

> And all of this goes to Cauldron, not 1.  I have never done an install of 1,
> but always Cauldron with daily updates and periodic (~ every three weeks or
> so ) fresh installs.
On this initial bug report Mageia was providing the « old » 0.8.x
version which in fact was only available in mageia 1 since dmorgan
updated it to the 0.9 beta series once he started the migration to
gnome3.

>> The bug was reported the 2011-07-15 while nm was updated to the beta 0.9
>> the
>> 2011-06-14 by dmorgan.
>> The support for ifcfg files  (aka respect the  NM_CONTROLLED=no and what i
>> was
>> wrongly calling support in sysvinit) was added by blino on 2011-07-31 by
>> patching the redhat plugin.
>> > From the log you did past in comment #1 we can see that NM&  sysvinit
>> > are
>> trying to put on the same interface.
>> You never explicity wrote that you have in your nm to control your wifi
>> interface from what you write&  since i can see ifplug running i can
>> expect
>> that you were using by default sysvinit script&  not nm.
[...]
>
> Just to clarify, none of these errors is specific to system startup.  All of
> them and all of the doc I included in my bugreports was taken from attempts
> to activate the interface *after* bootup.  So I still don't see what
> sysvinit would have to do with it.
Add said earlier i wrongly used the term of sysvinit when talking
abouf the ifcfg-.

>> You never explicity wrote that you have in your nm to control your wifi
>> interface from what you write&  since i can see ifplug running i can
>> expect
>> that you were using by default sysvinit script&  not nm
>
> I'm not sure what you mean by this.  "in your nm" would imply that I
> modified some NM-specific config file, which I assure you I did not.  I
>  have never done anything NM-specific to control NM.  The only things not
> done indirectly by NM itself or net-applet were my settings of NM_CONTROLLED
> and NEEDHOSTNAME in the ifcfg.
I wrote too fast here.
I meant that you never wrote somewhere that you choose to use nm
(especially since i can notice that ifplugd was playing with nm in the
logs).

> If there's an NM config option here that's out-of-line, it's Mageia that's
> putting it there, not me.
>
>>
>> Then if nm does not respect the NM_CONTROLLED=no (using the rhkeyfile
>> plugin)
>> then it should be reported&  assigned to blino.
>
> I agree but realize that if I have to use this to begin with, there's an NM
> bug that is potentially severe enough to prevent distro deployment.
I do understand & that's why i suggested you to use the keyfile plugin
in #865 instead of the « ifcfg-mdv plugin not maintained anymore in
0.8.x » or the rh plugin which also lacks some functionnality.

> Really, guys, I sympathize with the desire to move to something newer
> supported by others.  But you have to be ready to deal with the issue of
> back-breakage.
I personally don't care if Mageia wants to switch to nm or stick to
drakx-net, i was here to comment some bugs linked by you here.
Nm is provided by mageia and it's far than enough for me because i'm
able to use it without problem since Mageia 1. So as long as we have
someone to deal/maintain with drakx-net we can still follow this road.
[...]
>
> Blowing away the wireless capability of a significant portion of the
> community and then sitting back and saying stuff like "well it was a beta"
> or "we have to wait for upstream to fix that" doesn't cut it.   This isn't
> just a blind rebuild of some stable package that doesn't warrant preliminary
> testing.  It's a major piece of the distro infrastructure, and you shouldn't
> be doing changes like that unless
Again here could you please test with the *keyfile* plugin & if it's
still broken with the native plugin report it upstream so we can get a
bug fix for it ? (yes yet another fingers @ upstream :p )




-- 
Balcaen John
Jabber-id: mikala at jabber.littleboboy.net