|
发表于 2010-8-20 20:26:55
|
显示全部楼层
The short story is, the
kernel checks that either:
- you are the superuser
- you own the current tty
What this means is that root can always make beep work (to the best of
my knowledge!), and that any local user can make beep work, BUT a non-
root remote user cannot use beep in it’s natural state. What’s worse,
an xterm, or other x-session counts, as far as the kernel is concerned,
as ’remote’, so beep won’t work from a non-priviledged xterm either. I
had originally chalked this up to a bug, but there’s actually nothing I
can do about it, and it really is a Good Thing that the kernel does
things this way. There is also a solution. |
|