linux-kernel - Re: Recent wireless breakage (ipw2200, iwconfig, NetworkManager)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <5640c7e00703041646w32d7bc77s33d1fca4755a1b78@mail.gmail.com>
Date:	Mon, 5 Mar 2007 13:46:36 +1300
From:	"Ian McDonald" <ian.mcdonald@...di.co.nz>
To:	"Matt Mackall" <mpm@...enic.com>
Cc:	"Johannes Berg" <johannes@...solutions.net>,
	"Greg KH" <greg@...ah.com>, linux-kernel@...r.kernel.org,
	netdev@...r.kernel.org, yi.zhu@...el.com, jketreno@...ux.intel.com,
	linux-wireless <linux-wireless@...r.kernel.org>, akpm@...l.org
Subject: Re: Recent wireless breakage (ipw2200, iwconfig, NetworkManager)

On 3/5/07, Matt Mackall <mpm@...enic.com> wrote:
> > This is due to the recent sysfs restructuring I think. IIRC the fix is
> > to upgrade hal to a current git version.
>
> If that's the cause, the fix is to back out whatever was done to break
> userspace. Breaking userspace is not ok. Upgrading from 2.6.x to
> 2.6.x+1 should not entail replacing substantial parts of userspace,
> especially with NOT-EVEN-FRAKKING-RELEASED-YET CODE.
>
> I will try a new HAL when it shows up in Debian/unstable and not a
> moment sooner.
>
But you're running a kernel that's not in Debian/unstable so this
seems a bit hypocritical.

When you work with bleeding edge kernels you have to be prepared to
work around things. Hell for ages git wasn't in Debian - unstable
even, udev would break things etc.

Just my 2c worth.
-- 
Web: http://wand.net.nz/~iam4
Blog: http://iansblog.jandi.co.nz
WAND Network Research Group
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/