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] [day] [month] [year] [list]
Message-Id: <1166455210.3365.1050.camel@laptopd505.fenrus.org>
Date:	Mon, 18 Dec 2006 16:20:10 +0100
From:	Arjan van de Ven <arjan@...radead.org>
To:	Krzysztof Halasa <khc@...waw.pl>
Cc:	James Bottomley <James.Bottomley@...elEye.com>,
	Adrian Bunk <bunk@...sta.de>, Andrew Morton <akpm@...l.org>,
	linux-scsi@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [2.6 patch] remove the broken SCSI_SEAGATE driver

On Mon, 2006-12-18 at 14:48 +0100, Krzysztof Halasa wrote:
> Arjan van de Ven <arjan@...radead.org> writes:
> 
> > if a tree falls in a forest but there's nobody around to hear it, does
> > it make a sound?
> >
> > This sort of heisenbug questions aren't solved by "nobody hears it so
> > lets chop down the forest to make houses out of the wood" answers...
> 
> Does that mean you don't want to know which hardware/drivers aren't used
> anymore and which ones are?

it means that IT DOESN'T MATTER.
* If it's entirely unused, we get no bugreports -> there is no problem.
* If it's used but good quality, we get no bugreports -> there is no
problem

we can't distinguish the two. But.. in neither case is there a problem
so why force anything? I know some people don't like Heisenberg
uncertainty, but... personally for me if the effect is the same I
couldn't care less.

-- 
if you want to mail me at work (you don't), use arjan (at) linux.intel.com
Test the interaction between Linux and your BIOS via http://www.linuxfirmwarekit.org

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ