linux-kernel - Re: 22bb1be4d27... breaks hal (and NM)

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: <1216902124.7257.325.camel@twins>
Date:	Thu, 24 Jul 2008 14:22:04 +0200
From:	Peter Zijlstra <peterz@...radead.org>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	Johannes Berg <johannes@...solutions.net>,
	Pierre Ossman <drzeus-list@...eus.cx>,
	"John W. Linville" <linville@...driver.com>,
	Jean Tourrilhes <jt@....hp.com>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: 22bb1be4d27... breaks hal (and NM)

On Thu, 2008-07-24 at 05:11 -0700, Andrew Morton wrote:
> On Thu, 24 Jul 2008 13:57:11 +0200 Peter Zijlstra <peterz@...radead.org> wrote:
> 
> > On Thu, 2008-07-24 at 13:38 +0200, Johannes Berg wrote:
> > > On Thu, 2008-07-24 at 11:58 +0200, Pierre Ossman wrote:
> > > > From commit 22bb1be4d27...:
> > > > 
> > > > "The /sys/class/net/*/wireless/ direcory is, as far as I know, not used
> > > > by anyone."
> > > > 
> > > > Can't have been much of an investigation as HAL uses these to determine
> > > > if a card is a wireless one. Without this option, you cannot get
> > > > wireless support in NetworkManager, stranding most laptops.
> > > 
> > > Bzzzzt. You suck. Go check again. Hint: try hal's git tree.
> 
> err,
> 
> a) don't be rude
> 
> b) what's in various git trees is unuseful for making decisions
>    about production kernel features.
> 
> otoh the patch seems reasonable.

> So if you've enabled CONFIG_WIRELESS_EXT_SYSFS (and it correctly has
> default y) then things should continue to work OK.  And the deprecation
> date of 2010 sounds reasonable.  In fact generous, for us...
> 
> So where's the problem?

Your two previous points, a and b.

That help text should really have mentioned current software, not future
software. And the tone of the reply.

--
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/