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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
