Package: beep Version: 1.2.2-17 Followup-For: Bug #354694 I can confirm that release -17 does not work here either, by default. It has to do with the change in the last release between using evdev as the default device. Specifying the device on the command line:
% beep -e /dev/tty0 -f 1000 -n -f 2000 -n -f 1500 works fine. I have /dev/input/event0 on my system: % ls -l /dev/input/ total 0 crw-rw---- 1 root root 13, 64 Jan 1 1970 event0 crw-rw---- 1 root root 13, 65 Jan 1 1970 event1 crw-rw---- 1 root root 13, 66 Jan 1 1970 event2 crw-rw---- 1 root root 13, 67 Jan 1 1970 event3 crw-rw---- 1 root root 13, 63 Jan 1 1970 mice crw-rw---- 1 root root 13, 32 Jan 1 1970 mouse0 crw-r--r-- 1 root root 13, 128 Jan 1 1970 ts0 crw-r--r-- 1 root root 13, 144 Jan 1 1970 tsraw0 I am using the last stable kernel from Sarge, otherwise my system is Etch. I am using devfs, if that makes any difference. Lastly, "printf '\a'" *does* produce a beep. Hope this helps. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (900, 'testing'), (500, 'unstable'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.12-1-k7 Locale: LANG=C, LC_CTYPE=en_GB (charmap=ISO-8859-1) Versions of packages beep depends on: ii debconf [debconf-2.0] 1.4.71 Debian configuration management sy ii libc6 2.3.5-13 GNU C Library: Shared libraries an beep recommends no packages. -- debconf information: * beep/suid_option: suid root with only group audio executable -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
