Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757721AbXFLUhG (ORCPT ); Tue, 12 Jun 2007 16:37:06 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1756539AbXFLUg4 (ORCPT ); Tue, 12 Jun 2007 16:36:56 -0400 Received: from sovereign.computergmbh.de ([85.214.69.204]:2980 "EHLO sovereign.computergmbh.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753859AbXFLUg4 (ORCPT ); Tue, 12 Jun 2007 16:36:56 -0400 Date: Tue, 12 Jun 2007 22:36:55 +0200 (CEST) From: Jan Engelhardt To: "R.F. Burns" cc: Lee Revell , linux-kernel@vger.kernel.org Subject: Re: PC speaker In-Reply-To: Message-ID: References: <75b66ecd0706120744g7cdb3392l6537b5c68c2d6b21@mail.gmail.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1025 Lines: 28 On Jun 12 2007 16:25, R.F. Burns wrote: > > However, over the past several weeks, the students have found more > creative ways to abuse the PC speaker (outside of the OS.) The Powers > that Be are asking that the PC speakers be disabled completely. With > the small number of techs we have, it would be very impractical to go > around to all systems and remove the PC speaker from each and every > computer case. But you only have to do it once anyway. > So, the idea was raised about seeing if there was a way to blow the PC > speaker by loading a kernel module. If so, a mass-deployment of a > kernel module overnight would take care of the PC speaker problem once > and for all. And once you need a speaker (BIOS beep codes come to mind), you don't have any. Jan -- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/