On Sunday 27 November 2011 02.02:54 Paul Hartman wrote: > On Fri, Nov 25, 2011 at 4:58 PM, Allan Gottlieb <gottl...@nyu.edu> wrote: > > In the last day or two wicd broke badly due to a net-tools upgrade. > > > > The recommended workarounds are to specify USE=old-output > > for net-tools or to downgrade net-tools one version (I am ~amd64). > > > > Neither of these have helped me. Wicd cannot start either the > > wired or wireless interface. > > I have no solution, but just a "me too" that wicd-based networking > stopped working entirely after I emerged some updates a couple days > ago. My short-term "solution" was just stop wicd and use the old-style > net init script instead since I haven't had time to research any this > weekend yet.
I had the same issue after upgrading net-tools, wicd stoped working. While googling for a solution I found a workaround: Use the "ioctl" backend instead of the "external" backend. For me this workaround works. -- Dan Johansson, <http://www.dmj.nu> *************************************************** This message is printed on 100% recycled electrons! ***************************************************
