Have NetworkManager disabled by default when... (was: Recommends for metapackages)

2012-07-18 Thread Vincent Lefevre
On 2012-07-14 22:59:35 +0200, Tollef Fog Heen wrote: Due to those drawbacks, I've wondered why people don't just disable NetworkManager on their system instead of bothering with workarounds like the above or dpkg -P --force-depends and similar. Sorry for being late in the discussion. I also

Re: Have NetworkManager disabled by default when... (was: Recommends for metapackages)

2012-07-18 Thread Adam Borowski
On Wed, Jul 18, 2012 at 02:18:12PM +0200, Vincent Lefevre wrote: On 2012-07-14 22:59:35 +0200, Tollef Fog Heen wrote: Due to those drawbacks, I've wondered why people don't just disable NetworkManager on their system instead of bothering with workarounds like the above or dpkg -P

Re: Have NetworkManager disabled by default when... (was: Recommends for metapackages)

2012-07-18 Thread Vincent Lefevre
On 2012-07-18 15:01:43 +0200, Adam Borowski wrote: On Wed, Jul 18, 2012 at 02:18:12PM +0200, Vincent Lefevre wrote: Sorry for being late in the discussion. I also think that having NetworkManager disabled for those who do not want to use it is a good solution. But I think that if other

Re: Have NetworkManager disabled by default when... (was: Recommends for metapackages)

2012-07-18 Thread Philipp Kern
On Wed, Jul 18, 2012 at 03:01:43PM +0200, Adam Borowski wrote: wicd is used only on machines that use wifi, this excludes most desktops. wicd can also be used to manage different Ethernet configurations. Kind regards Philipp Kern signature.asc Description: Digital signature

Re: Have NetworkManager disabled by default when... (was: Recommends for metapackages)

2012-07-18 Thread Jon Dowland
On Wed, Jul 18, 2012 at 03:31:37PM +0200, Vincent Lefevre wrote: Still, the check would be useful on laptops where wicd is installed and enabled (the user could have a default ifupdown config and wicd enabled). What happens if neither wicd nor network-manager are installed, and then both are

Re: Have NetworkManager disabled by default when... (was: Recommends for metapackages)

2012-07-18 Thread Andrei POPESCU
On Mi, 18 iul 12, 15:01:43, Adam Borowski wrote: A different idea would be to have NM configured by default to do what it can do well (wifi) and stay away from all other interfaces, but because it has thorough assumptions that it controls all of networking in the system, this is not a change

Re: Have NetworkManager disabled by default when... (was: Recommends for metapackages)

2012-07-18 Thread Wookey
+++ Andrei POPESCU [2012-07-18 20:56 +0300]: On Mi, 18 iul 12, 15:01:43, Adam Borowski wrote: A different idea would be to have NM configured by default to do what it can do well (wifi) and stay away from all other interfaces, but because it has thorough assumptions that it controls all

Re: Have NetworkManager disabled by default when... (was: Recommends for metapackages)

2012-07-18 Thread Vincent Lefevre
On 2012-07-18 21:32:31 +0100, Wookey wrote: +++ Andrei POPESCU [2012-07-18 20:56 +0300]: One of the reasons I'm using network-manager instead of wicd or even plain ifupdown is the possibility to switch (more or less) seamlessly between wired and wifi. wicd does this just fine too. Tell

Re: Have NetworkManager disabled by default when... (was: Recommends for metapackages)

2012-07-18 Thread Andrei POPESCU
On Mi, 18 iul 12, 21:32:31, Wookey wrote: One of the reasons I'm using network-manager instead of wicd or even plain ifupdown is the possibility to switch (more or less) seamlessly between wired and wifi. wicd does this just fine too. In the past I've had problems with wicd in this