Debian Bug Tracking System wrote:
What doc please?
snoopy:~$ grep -i input /usr/share/doc/pommed/*
snoopy:~$
Double-checked that the README is indeed installed and contains what
it should contain.
Moreover, if you had read the manpage and ran pommed -f you would have
spotted a pretty clear error message about uinput.
I consider the beep feature to be a somewhat "advanced" feature in
that most people really don't care and don't want it anyway; that's
why it's disabled by default.
There are many, many people who use it. Only the windows users say "we
don't need this, because the most people don't care" :o)
Anything else just works out of the box and that's how it should be.
Would you mind if you integrate this patch to the README file?
Regards,
--
Eugen Dedu
--- /usr/share/doc/pommed/README 2008-01-23 14:33:31.000000000 +0100
+++ README 2008-02-11 10:28:18.000000000 +0100
@@ -4,6 +4,7 @@
- Kernel version requirements
- Supported machines
- Using pommed
+ - Doing beep
- Using gpomme and wmpomme
@@ -64,7 +65,21 @@
Using pommed
------------
-Launch pommed at startup, a simple init script will do.
+Launch pommed at startup, a simple init script will do. In the debian
+package this is done automatically, so you have nothing to do.
+
+
+Doing beep
+----------
+
+The beep works only if the uinput module is loaded. You can check if it
+is loaded with "lsmod | grep uinput". If it is not loaded, load it manually
+with "modprobe uinput" or automatically by putting it in /etc/modules (or
+something like this).
+
+How the beep works: Basically pommed creates an input device in userspace
+which handles beep events and the kernel happily passes them along, then all
+pommed have to do is ... well, *beep*.
Using gpomme and wmpomme
