mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kyle Moffett <mrmacman_g4@mac.com>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Stas Sergeev <stsp@aknet.ru>,
	7eggert@gmx.de, dtor_core@ameritech.net,
	Linux kernel <linux-kernel@vger.kernel.org>,
	vojtech@suse.cz
Subject: Re: [patch 1/1] pc-speaker: add SND_SILENT
Date: Sun, 26 Mar 2006 15:15:17 -0500	[thread overview]
Message-ID: <309A3D25-3FF3-421A-AA64-BC35D1230D58@mac.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0603262042400.28657@yvahk01.tjqt.qr>

On Mar 26, 2006, at 13:46:24, Jan Engelhardt wrote:
> I like the current approach, that is, load pcspkr to get a beep,  
> load pcspkr+snd-pcsp to get the full blow.
>
> On some servers, I need a mixture of when to allow a beep and when  
> not. In these, I patched the oops and panic functions to make a  
> sound, which implies that pcspkr.ko must be loaded. In turn, I  
> modified vt.c to have the default bell time = 0 to shut /bin/*sh  
> up. Works good.

In a lab I used to run we had a bunch of Linux workstations where  
some users tended to abuse the console beeper.  Our solution was a  
small kernel patch to add a CAP_VT_BEEP which was checked in the  
various console functions before generating a sound or modifying the  
default beep settings.  This allowed our automated hourly chimes to  
run without interference (run from cron as root), while preventing  
users not in the audio group from making sounds (/usr/bin/beep was  
root:audio 04750).

Cheers,
Kyle Moffett


  reply	other threads:[~2006-03-26 20:15 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5TCqf-E6-49@gated-at.bofh.it>
     [not found] ` <5TCqf-E6-51@gated-at.bofh.it>
     [not found]   ` <5TCqf-E6-53@gated-at.bofh.it>
     [not found]     ` <5TCqg-E6-55@gated-at.bofh.it>
     [not found]       ` <5TCqf-E6-47@gated-at.bofh.it>
2006-03-24 22:43         ` Bodo Eggert
2006-03-26  9:52           ` Stas Sergeev
2006-03-26 11:24             ` Bodo Eggert
2006-03-26 18:46             ` Jan Engelhardt
2006-03-26 20:15               ` Kyle Moffett [this message]
2006-03-27 16:34             ` Dmitry Torokhov
2006-03-27 17:36               ` Stas Sergeev
2006-04-08  8:02               ` Stas Sergeev
2006-03-28 18:31             ` Joseph Fannin
2006-03-28 18:43               ` Bodo Eggert
2006-03-28 18:51                 ` Vojtech Pavlik
2006-03-30 23:07                   ` Edgar Toernig
2006-03-31  7:46                     ` Vojtech Pavlik
2006-03-31 21:06                       ` Edgar Toernig
2006-04-01  6:11                         ` Vojtech Pavlik
     [not found] <200603220652.k2M6qZgi020656@shell0.pdx.osdl.net>
     [not found] ` <d120d5000603221332n6a6f9208x5651dc9ec993f4bf@mail.gmail.com>
     [not found]   ` <4422318C.407@aknet.ru>
     [not found]     ` <d120d5000603230651p6b43aad9ocad1aa3c2b51b388@mail.gmail.com>
2006-03-23 18:03       ` Stas Sergeev
2006-03-23 18:12         ` Dmitry Torokhov
2006-03-23 18:31           ` Stas Sergeev
2006-03-23 18:47             ` Dmitry Torokhov
2006-03-23 19:34               ` Stas Sergeev
2006-03-23 20:36                 ` Dmitry Torokhov
2006-03-24  4:59                   ` Stas Sergeev

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=309A3D25-3FF3-421A-AA64-BC35D1230D58@mac.com \
    --to=mrmacman_g4@mac.com \
    --cc=7eggert@gmx.de \
    --cc=dtor_core@ameritech.net \
    --cc=jengelh@linux01.gwdg.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stsp@aknet.ru \
    --cc=vojtech@suse.cz \
    /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®