On Wed, 4 Jul 2018 at 02:53:05 -0700 Jimmy Johnson <field.engin...@gmail.com> wrote:
> On 07/04/2018 02:28 AM, KatolaZ wrote: >> On Wed, Jul 04, 2018 at 02:15:46AM -0700, Jimmy Johnson wrote: >> >> [cut] >> >>>> >>>> I used wicd for several years, and I had always to swear against the >>>> gods of three or four religions to have it do what I wanted. The >>>> hardest thing was to convince wicd that I wanted a *specific* wi-fi >>>> connection among the several available: it kept choosing what it >>>> preferred, probably on the basis of "signal strength", and kept >>>> disconnecting and reconecting every time somebody entered the room or >>>> moved a chair. I had to manually disable the connections I didn't want >>>> to use, then manually re-enable them. >>> >>> >>> That sounds like network manager was installed at the time and not a wicd >>> problem, wicd gets blamed because you can see it in your tray, while NM >>> is in the background messing with your connection. >>> >>> I may be wrong but I don't think network manager is good or helpful in >>> any way, causes way to many problems and confusion for the average user. >>> >> >> I don't know about you, but I always know exactly, at any point in >> time, what software is installed in my system. And I am 100% sure that >> network-manager has *never* been installed in any of the machines I >> have administered or used in the last 20 years :) >> >> So the fault was genuinely due to wicd, and my swearing was more than >> justified ;) > > > If network/interfaces is not configured then wicd will not work. That I know of, network/interfaces does not depend on NM. I do have it, it works fine on all my Ascii systems, and just like KatolaZ "I am 100% sure that network-manager has *never* been installed in any of the machines I have administered or used in the last 20 years :)" (lol, BTW). Alessandro _______________________________________________ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
