On Sun, May 27, 2018 at 06:42:57PM +0200, Adam Borowski wrote:

[cut]

>
> This is actually very puzzling: what we want, is a wrapper for iw which
> seeks available wifi networks, and provides a GUI to choose one. The only
> reason such a tool would ever look at eth0 is to see if its link is up, and
> if so, skip wifi unless explicitly told to connect anyway.
>
> So why do authors of such tools feel the need to control the state of
> non-wifi interfaces?
>
>

Because programmers think that writing a program that does more things
than repuired is *better*. That's actually the cause of bigger
problems than wicd wanting to manage eth0...

HND

KatolaZ

-- 
[ ~.,_  Enzo Nicosia aka KatolaZ - Devuan -- Freaknet Medialab  ]  
[     "+.  katolaz [at] freaknet.org --- katolaz [at] yahoo.it  ]
[       @)   http://kalos.mine.nu ---  Devuan GNU + Linux User  ]
[     @@)  http://maths.qmul.ac.uk/~vnicosia --  GPG: 0B5F062F  ] 
[ (@@@)  Twitter: @KatolaZ - skype: katolaz -- github: KatolaZ  ]