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: <20081026200939.GC12648@tuxdriver.com>
Date:	Sun, 26 Oct 2008 16:09:39 -0400
From:	"John W. Linville" <linville@...driver.com>
To:	Arjan van de Ven <arjan@...radead.org>
Cc:	torvalds@...ux-foundation.org, netdev@...r.kernel.org,
	linux-kernel@...r.kernel.org, rjw@...k.pl, rodriguez@...eros.com,
	johannes@...solutions.net
Subject: Re: [PATCH] wireless: fix regression caused by regulatory config
	option

On Sun, Oct 26, 2008 at 10:30:24AM -0700, Arjan van de Ven wrote:
> From 9095a0f6005a8f50c79e51f4aaceda95e361a891 Mon Sep 17 00:00:00 2001
> From: Arjan van de Ven <arjan@...ux.intel.com>
> Date: Sun, 26 Oct 2008 10:25:30 -0700
> Subject: [PATCH] wireless: fix regression caused by regulatory config option
> 
> The default for the regulatory compatibility option is wrong;
> if you picked the default you ended up with a non-functional wifi
> system (at least I did on Fedora 9 with iwl4965).
> I don't think even the October 2008 releases of the various distros
> has the new userland so clearly the default is wrong, and also
> we can't just go about deleting this in 2.6.29...
> 
> Change the default to "y" and also adjust the config text a little to
> reflect this.

Is it common practice to have compatibility options default to
"y"?  I'm not saying it shouldn't be, just wondering if it has been
traditionally?

John
-- 
John W. Linville		Linux should be at the core
linville@...driver.com			of your literate lifestyle.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ