diff options
Diffstat (limited to 'zarb-ml/mageia-dev/attachments/20121124')
14 files changed, 234 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/attachments/20121124/3834c173/attachment-0001.html b/zarb-ml/mageia-dev/attachments/20121124/3834c173/attachment-0001.html new file mode 100644 index 000000000..80e80b7e1 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20121124/3834c173/attachment-0001.html @@ -0,0 +1,23 @@ +I don't have problem with people working in Mageia improvements and receive payment for it, because this improvement will be free software.<br><br>I remembered this blogpost about payment to develop poppler/Okular features - <a href="http://tsdgeos.blogspot.com.br/2012/06/free-software-free-to-pay.html">http://tsdgeos.blogspot.com.br/2012/06/free-software-free-to-pay.html</a><br> +<br><div class="gmail_quote">2012/11/24 Sander Lepik <span dir="ltr"><<a href="mailto:sander.lepik@eesti.ee" target="_blank">sander.lepik@eesti.ee</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> +24.11.2012 18:55, PhilippeDidier kirjutas:<br> +<div class="im">> NO !<br> +> You mean someone is paid and create a third repo for something Mageia<br> +> doesn't want to import...<br> +><br> +> If that thing brings a mess into Mageia, we will see bug reports in<br> +> bugzilla and lot of time lost by Mageia bug-triagers, devs, packagers,<br> +> before discovering that is not a Mageia problem but that this stuff<br> +> brought some shit !<br> +> We suffer of lack of time... and this will consume more time from<br> +> voluntary contributors to repair something badly done by someone that<br> +> was paid for it !<br> +</div>Well, we have such repos already today and you can't stop something like that. But you saw<br> +my example the wrong way. Mageia doesn't have to support those repos and problems caused by<br> +such packages. I don't like such repos either and i hope that paid people fix things in our<br> +repos.<br> +<br> +--<br> +Sander<br> +<br> +</blockquote></div><br><br clear="all"><br>-- <br>Filipe Saraiva<br><a href="http://filipesaraiva.info/" target="_blank">http://filipesaraiva.info/</a><br> diff --git a/zarb-ml/mageia-dev/attachments/20121124/3834c173/attachment.html b/zarb-ml/mageia-dev/attachments/20121124/3834c173/attachment.html new file mode 100644 index 000000000..80e80b7e1 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20121124/3834c173/attachment.html @@ -0,0 +1,23 @@ +I don't have problem with people working in Mageia improvements and receive payment for it, because this improvement will be free software.<br><br>I remembered this blogpost about payment to develop poppler/Okular features - <a href="http://tsdgeos.blogspot.com.br/2012/06/free-software-free-to-pay.html">http://tsdgeos.blogspot.com.br/2012/06/free-software-free-to-pay.html</a><br> +<br><div class="gmail_quote">2012/11/24 Sander Lepik <span dir="ltr"><<a href="mailto:sander.lepik@eesti.ee" target="_blank">sander.lepik@eesti.ee</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> +24.11.2012 18:55, PhilippeDidier kirjutas:<br> +<div class="im">> NO !<br> +> You mean someone is paid and create a third repo for something Mageia<br> +> doesn't want to import...<br> +><br> +> If that thing brings a mess into Mageia, we will see bug reports in<br> +> bugzilla and lot of time lost by Mageia bug-triagers, devs, packagers,<br> +> before discovering that is not a Mageia problem but that this stuff<br> +> brought some shit !<br> +> We suffer of lack of time... and this will consume more time from<br> +> voluntary contributors to repair something badly done by someone that<br> +> was paid for it !<br> +</div>Well, we have such repos already today and you can't stop something like that. But you saw<br> +my example the wrong way. Mageia doesn't have to support those repos and problems caused by<br> +such packages. I don't like such repos either and i hope that paid people fix things in our<br> +repos.<br> +<br> +--<br> +Sander<br> +<br> +</blockquote></div><br><br clear="all"><br>-- <br>Filipe Saraiva<br><a href="http://filipesaraiva.info/" target="_blank">http://filipesaraiva.info/</a><br> diff --git a/zarb-ml/mageia-dev/attachments/20121124/42dfe426/attachment-0001.html b/zarb-ml/mageia-dev/attachments/20121124/42dfe426/attachment-0001.html new file mode 100644 index 000000000..325c132a3 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20121124/42dfe426/attachment-0001.html @@ -0,0 +1,26 @@ +<br><div class="gmail_extra"><br><br><div class="gmail_quote">2012/11/24 Frank Griffin <span dir="ltr"><<a href="mailto:ftg@roadrunner.com" target="_blank">ftg@roadrunner.com</a>></span><br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"> + +<div class="im">On 11/24/2012 02:59 PM, John Balcaen wrote:<br> +<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"> +<br> +Suggest here: drop all ifcfg configuration files and switch to keyfile plugin.<br> +<br> +</blockquote> +<br></div> +OK, in the spirit of Anne's original question, can you tell us exactly what the keyfile plugin is and does, and how to use it ? I'll volunteer to do a fresh install and test it.<br> +</blockquote></div><br>The keyfile plugin as said earlier is the default & native plugin to use with networkmanager [1]</div><div class="gmail_extra">In order to introduce nm on distribution using ifcfg files (redhat/fedora) the ifcfg-rh plugin has been wrote to read & make nm able to use them (& avoid interferences between nm & the « old » scripts).</div> + +<div class="gmail_extra">So to use it you simply need to configure networkmanager by editing /etc/NetworkManager/NetworkManager.conf</div><div class="gmail_extra"><br></div><div class="gmail_extra">For example on my workstation i've got :</div> + +<div class="gmail_extra"><div class="gmail_extra">cat NetworkManager.conf </div><div class="gmail_extra">[main]</div><div class="gmail_extra">plugins=keyfile</div><div class="gmail_extra">dns=dnsmasq</div><div class="gmail_extra"> + +<br></div><div class="gmail_extra">[keyfile]</div><div class="gmail_extra">hostname=<a href="http://aker.cauldron.lan.littleboboy.net">aker.cauldron.lan.littleboboy.net</a></div><div class="gmail_extra"><br></div><div class="gmail_extra"> + +it's mean that i'm using the keyfile plugin (read [1] or man NetworkManager.conf for more details) & ask nm to to also start dnsmasq for me.</div><div class="gmail_extra">I also setup the hostname to set in nm in the keyfile section.</div> + +<div class="gmail_extra"><br></div><div class="gmail_extra">There's also no need to do a « fresh » install to test/use it. </div></div><div class="gmail_extra"><br></div><div class="gmail_extra"><br></div><div class="gmail_extra"> + +[1] <a href="https://live.gnome.org/NetworkManager/SystemSettings">https://live.gnome.org/NetworkManager/SystemSettings</a><br clear="all"><div><br></div>-- <br>Balcaen John<br>Jabber-id: <a href="mailto:mikala@jabber.littleboboy.net" target="_blank">mikala@jabber.littleboboy.net</a><br> + + +</div> diff --git a/zarb-ml/mageia-dev/attachments/20121124/42dfe426/attachment.html b/zarb-ml/mageia-dev/attachments/20121124/42dfe426/attachment.html new file mode 100644 index 000000000..325c132a3 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20121124/42dfe426/attachment.html @@ -0,0 +1,26 @@ +<br><div class="gmail_extra"><br><br><div class="gmail_quote">2012/11/24 Frank Griffin <span dir="ltr"><<a href="mailto:ftg@roadrunner.com" target="_blank">ftg@roadrunner.com</a>></span><br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"> + +<div class="im">On 11/24/2012 02:59 PM, John Balcaen wrote:<br> +<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"> +<br> +Suggest here: drop all ifcfg configuration files and switch to keyfile plugin.<br> +<br> +</blockquote> +<br></div> +OK, in the spirit of Anne's original question, can you tell us exactly what the keyfile plugin is and does, and how to use it ? I'll volunteer to do a fresh install and test it.<br> +</blockquote></div><br>The keyfile plugin as said earlier is the default & native plugin to use with networkmanager [1]</div><div class="gmail_extra">In order to introduce nm on distribution using ifcfg files (redhat/fedora) the ifcfg-rh plugin has been wrote to read & make nm able to use them (& avoid interferences between nm & the « old » scripts).</div> + +<div class="gmail_extra">So to use it you simply need to configure networkmanager by editing /etc/NetworkManager/NetworkManager.conf</div><div class="gmail_extra"><br></div><div class="gmail_extra">For example on my workstation i've got :</div> + +<div class="gmail_extra"><div class="gmail_extra">cat NetworkManager.conf </div><div class="gmail_extra">[main]</div><div class="gmail_extra">plugins=keyfile</div><div class="gmail_extra">dns=dnsmasq</div><div class="gmail_extra"> + +<br></div><div class="gmail_extra">[keyfile]</div><div class="gmail_extra">hostname=<a href="http://aker.cauldron.lan.littleboboy.net">aker.cauldron.lan.littleboboy.net</a></div><div class="gmail_extra"><br></div><div class="gmail_extra"> + +it's mean that i'm using the keyfile plugin (read [1] or man NetworkManager.conf for more details) & ask nm to to also start dnsmasq for me.</div><div class="gmail_extra">I also setup the hostname to set in nm in the keyfile section.</div> + +<div class="gmail_extra"><br></div><div class="gmail_extra">There's also no need to do a « fresh » install to test/use it. </div></div><div class="gmail_extra"><br></div><div class="gmail_extra"><br></div><div class="gmail_extra"> + +[1] <a href="https://live.gnome.org/NetworkManager/SystemSettings">https://live.gnome.org/NetworkManager/SystemSettings</a><br clear="all"><div><br></div>-- <br>Balcaen John<br>Jabber-id: <a href="mailto:mikala@jabber.littleboboy.net" target="_blank">mikala@jabber.littleboboy.net</a><br> + + +</div> diff --git a/zarb-ml/mageia-dev/attachments/20121124/7ce98fd7/attachment-0001.html b/zarb-ml/mageia-dev/attachments/20121124/7ce98fd7/attachment-0001.html new file mode 100644 index 000000000..d59848824 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20121124/7ce98fd7/attachment-0001.html @@ -0,0 +1,40 @@ +<p dir="ltr">Le 24 nov. 2012 16:39, "Frank Griffin" <<a href="mailto:ftg@roadrunner.com">ftg@roadrunner.com</a>> a écrit :<br> +><br> +> On 11/24/2012 02:37 AM, Anne Wilson wrote:<br> +>><br> +>> On 24/11/2012 05:36, Frank Griffin wrote:<br> +>>><br> +>>> I haven't tested since, because this was the straw on the camel's back<br> +>>> that finally got me to pull enough teeth to find out that NM won't work<br> +>>> in KDE without manual intervention.  Once I got NM to work, I never went<br> +>>> back.<br> +>><br> +>> For those of us still struggling to get wireless to work, can you give<br> +>> more details, please?  Sorry if you have done so somewhere else and I<br> +>> missed it.<br> +>><br> +> As I understand it, NM needs to parse ifcfg files to an internal format before it can work correctly with wireless.  I suspect there's a way to  do this with the NM CLI, but unless you speak NM well (I don't), it isn't really obvious.</p> + +<p dir="ltr">It's only happening if you choose to not change the default networkmanager configuration aka using the ifcfg plugin which means read only support for ifcfg files. I'm personally using instead the keyfile plugin (the upstream default).<br> + +><br> +> It's easy in GNOME, as GNOME appears to detect that it needs to be done and does it silently.  So if you have GNOME installed, just log in to it, activate the interface from the dropdown at the top right, and log out again.<br> +</p> +<p dir="ltr">> Otherwise, from KDE, you define the interface with drakconnect (MCC), selecting to allow NM to control it.  Then install plasma-applet-networkmanager (which is not installed by default for KDE because NM is not supposed to be the default for wireless yet). John Balcaen has posted that you don't need to add it to the panel (you can invoke it directly in some way I didn't follow), but before I read that I just used the panel toolbox widget  "Add Widgets" option, search on network", double-clicked to place it<br> + +> on the panel, and invoked it from there.  Just tell it to connect the wireless, and the parse should be done automatically.<br> +><br> +> IIRC, John also posted that knetworkmanager (invoked through KDE system settings) should do as well, but I'm not sure whether the plasma-applet-networkmanager package was still required in that case. </p> +<p dir="ltr">knetworkmanager is just the name of the source rpm and the original binary which is long dead...So currently it's just a virtual package pulling the plasma applet package. </p> +<p dir="ltr">> Something has probably changed since I did this, since my recollection is that the plasma applet showed a choice of interface controllers with NM selected by default, and that did the required parse.  In current cauldron, both the applet and knetworkmanager give me the same display, and neither mentions NM, so maybe both the panel icon and the system settings option are executing the same thing, and the plasma package was being used under the covers.<br> +</p> +<p dir="ltr">They're the same thing indeed. <br> +> I'm a recent refugee to KDE from GNOME3, so there's a lot I don't find intuitive.<br> +><br> +> There are two questions for which I don't have answers.<br> +><br> +> Once you've caused the parse to be done, you should be good to go for wireless on subsequent reboots for that SSID.  I'm not sure whether it needs to be redone if you switch SSIDs, but the errors you get from NM if the parse *hasn't* been done refer to errors in an "ifcfg-rh" which appears to be independent of SSID.  So maybe it's a one-time thing, or maybe it's a one-time-per-SSID thing.<br> + +></p> +<p dir="ltr">Suggest here: drop all ifcfg configuration files and switch to keyfile plugin. <br> +</p> diff --git a/zarb-ml/mageia-dev/attachments/20121124/7ce98fd7/attachment.html b/zarb-ml/mageia-dev/attachments/20121124/7ce98fd7/attachment.html new file mode 100644 index 000000000..d59848824 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20121124/7ce98fd7/attachment.html @@ -0,0 +1,40 @@ +<p dir="ltr">Le 24 nov. 2012 16:39, "Frank Griffin" <<a href="mailto:ftg@roadrunner.com">ftg@roadrunner.com</a>> a écrit :<br> +><br> +> On 11/24/2012 02:37 AM, Anne Wilson wrote:<br> +>><br> +>> On 24/11/2012 05:36, Frank Griffin wrote:<br> +>>><br> +>>> I haven't tested since, because this was the straw on the camel's back<br> +>>> that finally got me to pull enough teeth to find out that NM won't work<br> +>>> in KDE without manual intervention.  Once I got NM to work, I never went<br> +>>> back.<br> +>><br> +>> For those of us still struggling to get wireless to work, can you give<br> +>> more details, please?  Sorry if you have done so somewhere else and I<br> +>> missed it.<br> +>><br> +> As I understand it, NM needs to parse ifcfg files to an internal format before it can work correctly with wireless.  I suspect there's a way to  do this with the NM CLI, but unless you speak NM well (I don't), it isn't really obvious.</p> + +<p dir="ltr">It's only happening if you choose to not change the default networkmanager configuration aka using the ifcfg plugin which means read only support for ifcfg files. I'm personally using instead the keyfile plugin (the upstream default).<br> + +><br> +> It's easy in GNOME, as GNOME appears to detect that it needs to be done and does it silently.  So if you have GNOME installed, just log in to it, activate the interface from the dropdown at the top right, and log out again.<br> +</p> +<p dir="ltr">> Otherwise, from KDE, you define the interface with drakconnect (MCC), selecting to allow NM to control it.  Then install plasma-applet-networkmanager (which is not installed by default for KDE because NM is not supposed to be the default for wireless yet). John Balcaen has posted that you don't need to add it to the panel (you can invoke it directly in some way I didn't follow), but before I read that I just used the panel toolbox widget  "Add Widgets" option, search on network", double-clicked to place it<br> + +> on the panel, and invoked it from there.  Just tell it to connect the wireless, and the parse should be done automatically.<br> +><br> +> IIRC, John also posted that knetworkmanager (invoked through KDE system settings) should do as well, but I'm not sure whether the plasma-applet-networkmanager package was still required in that case. </p> +<p dir="ltr">knetworkmanager is just the name of the source rpm and the original binary which is long dead...So currently it's just a virtual package pulling the plasma applet package. </p> +<p dir="ltr">> Something has probably changed since I did this, since my recollection is that the plasma applet showed a choice of interface controllers with NM selected by default, and that did the required parse.  In current cauldron, both the applet and knetworkmanager give me the same display, and neither mentions NM, so maybe both the panel icon and the system settings option are executing the same thing, and the plasma package was being used under the covers.<br> +</p> +<p dir="ltr">They're the same thing indeed. <br> +> I'm a recent refugee to KDE from GNOME3, so there's a lot I don't find intuitive.<br> +><br> +> There are two questions for which I don't have answers.<br> +><br> +> Once you've caused the parse to be done, you should be good to go for wireless on subsequent reboots for that SSID.  I'm not sure whether it needs to be redone if you switch SSIDs, but the errors you get from NM if the parse *hasn't* been done refer to errors in an "ifcfg-rh" which appears to be independent of SSID.  So maybe it's a one-time thing, or maybe it's a one-time-per-SSID thing.<br> + +></p> +<p dir="ltr">Suggest here: drop all ifcfg configuration files and switch to keyfile plugin. <br> +</p> diff --git a/zarb-ml/mageia-dev/attachments/20121124/a04cc0a0/attachment-0001.asc b/zarb-ml/mageia-dev/attachments/20121124/a04cc0a0/attachment-0001.asc new file mode 100644 index 000000000..bcdd92f12 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20121124/a04cc0a0/attachment-0001.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v1.4.10 (GNU/Linux) + +iD8DBQBQsPb2T1rWTfpocyQRAvk1AKCCCFbBBCEWT3PG+BMICgI6Oei3agCdGHwz +rHHmsWQ/FxoHc3H9Gw0J1mI= +=3hiA +-----END PGP SIGNATURE----- diff --git a/zarb-ml/mageia-dev/attachments/20121124/a04cc0a0/attachment.asc b/zarb-ml/mageia-dev/attachments/20121124/a04cc0a0/attachment.asc new file mode 100644 index 000000000..bcdd92f12 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20121124/a04cc0a0/attachment.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v1.4.10 (GNU/Linux) + +iD8DBQBQsPb2T1rWTfpocyQRAvk1AKCCCFbBBCEWT3PG+BMICgI6Oei3agCdGHwz +rHHmsWQ/FxoHc3H9Gw0J1mI= +=3hiA +-----END PGP SIGNATURE----- diff --git a/zarb-ml/mageia-dev/attachments/20121124/bc233d5e/attachment-0001.asc b/zarb-ml/mageia-dev/attachments/20121124/bc233d5e/attachment-0001.asc new file mode 100644 index 000000000..c91238482 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20121124/bc233d5e/attachment-0001.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v1.4.10 (GNU/Linux) + +iD8DBQBQsN0LT1rWTfpocyQRAoVYAJ0UE3cTj6Hshv4b/odLLAuBQ/HfmgCfe3Bi +1JNxBWuIAUmHan/KcgIboDM= +=535c +-----END PGP SIGNATURE----- diff --git a/zarb-ml/mageia-dev/attachments/20121124/bc233d5e/attachment.asc b/zarb-ml/mageia-dev/attachments/20121124/bc233d5e/attachment.asc new file mode 100644 index 000000000..c91238482 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20121124/bc233d5e/attachment.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v1.4.10 (GNU/Linux) + +iD8DBQBQsN0LT1rWTfpocyQRAoVYAJ0UE3cTj6Hshv4b/odLLAuBQ/HfmgCfe3Bi +1JNxBWuIAUmHan/KcgIboDM= +=535c +-----END PGP SIGNATURE----- diff --git a/zarb-ml/mageia-dev/attachments/20121124/c443eda3/attachment-0001.asc b/zarb-ml/mageia-dev/attachments/20121124/c443eda3/attachment-0001.asc new file mode 100644 index 000000000..37baa4f4f --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20121124/c443eda3/attachment-0001.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v1.4.10 (GNU/Linux) + +iD8DBQBQsOqST1rWTfpocyQRAsaCAKCjytm1nIrI3+3EVTLBSiC5a+UqkQCgtriG +DPprP45XfLCRdG7VYys0Lws= +=pXYi +-----END PGP SIGNATURE----- diff --git a/zarb-ml/mageia-dev/attachments/20121124/c443eda3/attachment.asc b/zarb-ml/mageia-dev/attachments/20121124/c443eda3/attachment.asc new file mode 100644 index 000000000..37baa4f4f --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20121124/c443eda3/attachment.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v1.4.10 (GNU/Linux) + +iD8DBQBQsOqST1rWTfpocyQRAsaCAKCjytm1nIrI3+3EVTLBSiC5a+UqkQCgtriG +DPprP45XfLCRdG7VYys0Lws= +=pXYi +-----END PGP SIGNATURE----- diff --git a/zarb-ml/mageia-dev/attachments/20121124/ca9558d5/attachment-0001.asc b/zarb-ml/mageia-dev/attachments/20121124/ca9558d5/attachment-0001.asc new file mode 100644 index 000000000..6c763f595 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20121124/ca9558d5/attachment-0001.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v1.4.10 (GNU/Linux) + +iD8DBQBQsAHsT1rWTfpocyQRAi/AAJ9qTjFRwk2P1D5tXuH3MCb1bZUcHgCgj2Tp +OQ9n6B4/AULf2ysZnRUjKAo= +=TQQL +-----END PGP SIGNATURE----- diff --git a/zarb-ml/mageia-dev/attachments/20121124/ca9558d5/attachment.asc b/zarb-ml/mageia-dev/attachments/20121124/ca9558d5/attachment.asc new file mode 100644 index 000000000..6c763f595 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20121124/ca9558d5/attachment.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v1.4.10 (GNU/Linux) + +iD8DBQBQsAHsT1rWTfpocyQRAi/AAJ9qTjFRwk2P1D5tXuH3MCb1bZUcHgCgj2Tp +OQ9n6B4/AULf2ysZnRUjKAo= +=TQQL +-----END PGP SIGNATURE----- |