From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "R.F. Burns" <burnsrf@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PC speaker
Date: Sun, 13 Jun 2010 01:07:04 +0100 [thread overview]
Message-ID: <20100613010704.05e0b216@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <AANLkTim2QHHztN6Nyg8VEsd-vkpg5Sk4TajBT7Bt-ga4@mail.gmail.com>
On Sat, 12 Jun 2010 17:32:09 -0400
"R.F. Burns" <burnsrf@gmail.com> wrote:
> Is it possible to write a kernel module which, when loaded, will blow
> the PC speaker?
Not really. You can do damage to some PCs by attacking other bits of the
hardware (erasing the bios etc) but they are actually a lot better
protected nowdays then some years back.
If you don't have the root password and expertise I imagine throwing it
out of the window or feeding it iron filings will work just as well. That
is physical system access tends to imply you can break it.
next prev parent reply other threads:[~2010-06-12 23:58 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-12 21:32 R.F. Burns
2010-06-12 21:50 ` Daniel Hazelton
2010-06-13 0:07 ` Alan Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-06-13 3:04 R.F. Burns
2025-07-01 3:58 R.F. Burns
2024-06-12 20:16 R.F. Burns
2023-06-13 3:10 R.F. Burns
2022-06-12 22:29 R.F. Burns
2021-06-15 3:32 R.F. Burns
2021-06-24 14:21 ` Oleksandr Natalenko
2021-06-25 10:12 ` Oleksandr Natalenko
2020-06-18 17:49 R.F. Burns
2020-06-19 3:04 ` Randy Dunlap
2020-06-23 8:03 ` Oleksandr Natalenko
2019-06-13 16:16 R.F. Burns
2019-06-13 19:57 ` Theodore Ts'o
2019-06-13 20:07 ` Randy Dunlap
2018-06-12 20:31 R.F. Burns
2017-06-12 19:13 R.F. Burns
2017-06-12 21:25 ` Randy Dunlap
2017-06-12 22:52 ` Dmitry Torokhov
2016-08-05 16:51 R.F. Burns
2009-06-12 21:28 R.F. Burns
2009-06-12 21:40 ` Valdis.Kletnieks
2009-06-13 0:10 ` John Sheu
2008-07-08 17:08 R.F. Burns
2008-07-08 17:38 ` Jan Engelhardt
2007-06-12 12:45 R.F. Burns
2007-06-12 13:31 ` Jan Engelhardt
2007-06-12 13:54 ` R.F. Burns
2007-06-12 13:57 ` Jan Engelhardt
2007-06-12 15:09 ` Jan Engelhardt
2007-06-12 15:19 ` Alan Cox
2007-06-12 17:26 ` Jan Engelhardt
2007-06-12 20:08 ` David Schwartz
2007-06-12 20:34 ` Jan Engelhardt
2007-06-13 9:22 ` Helge Hafting
2007-06-13 10:27 ` Maciej W. Rozycki
2007-06-13 10:41 ` Paulo Marques
2007-06-13 19:53 ` Pavel Machek
2007-06-15 0:36 ` Kyle Moffett
2007-06-12 14:44 ` Lee Revell
2007-06-12 17:39 ` jimmy bahuleyan
2007-06-12 20:25 ` R.F. Burns
2007-06-12 20:36 ` Jan Engelhardt
2007-06-12 21:15 ` Clemens Koller
2007-06-12 22:08 ` David Schwartz
2007-06-13 12:26 ` Chris Smith
2007-06-15 17:07 ` Phillip Susi
2007-06-15 19:34 ` Jan Engelhardt
2007-06-15 23:30 ` Phillip Susi
2007-06-16 3:20 ` Kyle Moffett
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100613010704.05e0b216@lxorguk.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=burnsrf@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®