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
On Sun, Nov 27 2011, Dan Johansson wrote:
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
On Sun, 27 Nov 2011 13:27:59 +0100, Dan Johansson wrote:
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.
That explains why I was
On Nov 28, 2011 6:18 AM, Neil Bothwick n...@digimed.co.uk wrote:
On Sun, 27 Nov 2011 13:27:59 +0100, Dan Johansson wrote:
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
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
On Fri, Nov 25, 2011 at 2: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
On Fri, Nov 25 2011, Mark Knecht wrote:
On Fri, Nov 25, 2011 at 2: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
7 matches
Mail list logo
