[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <MDEHLPKNGKAHNMBLJOLKKEJJBPAD.davids@webmaster.com>
Date: Thu, 18 Dec 2008 16:45:32 -0800
From: "David Schwartz" <davids@...master.com>
To: "Herbert Xu" <herbert@...dor.apana.org.au>
Cc: <davem@...emloft.net>, <linux-kernel@...r.kernel.org>,
<netdev@...r.kernel.org>
Subject: RE: [PATCH] Stop scaring users with "treason uncloaked!"
> Most people won't actually think their printer is on fire. But most
> people WILL think there is serious cause for concern when they see this
> for the first time in dmesg. Many will search the net for explanations
> and come away confused and not entirely reassured. And at least one
> clueless guy will call the police because he still thinks he's under
> attack.
Messages about something or other being "illegal" occur about 345 times in
the Linux kernel source code. Are we going to start patching those too?
We have "illegal norm", "illegal input", "illegal call", "illegal type",
"illegal bits", "illegal root port number", "illegal host number", "illegal
DMA data", "illegal dimensions" (who do you call about that one?), "illegal
phase", "illegal page number", "illegal seek", and on, and on, and on.
I suspect that if I submitted a patch to change all of those to "invalid",
I'd be considered a kook. (Well, more of a kook, anyway.)
DS
--
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