From: Phillip Susi <psusi@cfl.rr.com>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: "R.F. Burns" <burnsrf@gmail.com>,
Lee Revell <rlrevell@joe-job.com>,
linux-kernel@vger.kernel.org
Subject: Re: PC speaker
Date: Fri, 15 Jun 2007 19:30:51 -0400 [thread overview]
Message-ID: <4673212B.5010304@cfl.rr.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0706152131450.32724@fbirervta.pbzchgretzou.qr>
Jan Engelhardt wrote:
> On Jun 15 2007 13:07, Phillip Susi wrote:
>> 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.
>> Now I am curious; how are they getting the pc speaker to make any sound with
>> the kernel module disabled?
>
> ioperm(), inb(), and outb() from userspace. Needs root, though. Or
> /dev/port, with write. Which comes to the question how they gained root.
> Perhaps live cd? In which case, the OP should, as recommended in this
> thread already, deactivate choosing boot devices, if that's possible.
>
> (Unfortunately, newer BIOSes with 'integrated bootmenu' with F8 or so,
> but I have not seen a way to deactivate _that_ menu.)
He already said they don't have root access and that allowed him to stop
them from accessing the sound card by setting appropriate permissions.
next prev parent reply other threads:[~2007-06-15 23:30 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-12 12:45 PC speaker 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 [this message]
2007-06-16 3:20 ` Kyle Moffett
-- strict thread matches above, loose matches on Subject: below --
2008-07-08 17:08 R.F. Burns
2008-07-08 17:38 ` Jan Engelhardt
2009-06-12 21:28 R.F. Burns
2009-06-12 21:40 ` Valdis.Kletnieks
2009-06-13 0:10 ` John Sheu
2010-06-12 21:32 R.F. Burns
2010-06-12 21:50 ` Daniel Hazelton
2010-06-13 0:07 ` Alan Cox
2016-08-05 16:51 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
2018-06-12 20:31 R.F. Burns
2019-06-13 16:16 R.F. Burns
2019-06-13 19:57 ` Theodore Ts'o
2019-06-13 20:07 ` Randy Dunlap
2020-06-18 17:49 R.F. Burns
2020-06-19 3:04 ` Randy Dunlap
2020-06-23 8:03 ` Oleksandr Natalenko
2021-06-15 3:32 R.F. Burns
2021-06-24 14:21 ` Oleksandr Natalenko
2021-06-25 10:12 ` Oleksandr Natalenko
2022-06-12 22:29 R.F. Burns
2023-06-13 3:10 R.F. Burns
2024-06-12 20:16 R.F. Burns
2025-07-01 3:58 R.F. Burns
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=4673212B.5010304@cfl.rr.com \
--to=psusi@cfl.rr.com \
--cc=burnsrf@gmail.com \
--cc=jengelh@computergmbh.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rlrevell@joe-job.com \
/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