[Pommed-commits] r443 - trunk

[jblache at alioth.debian.org]

Author: jblache
Date: 2008-02-27 19:52:54 +0000 (Wed, 27 Feb 2008)
New Revision: 443

Modified:
   trunk/README
Log:
Add a note about the beeper feature.


Modified: trunk/README
===================================================================
--- trunk/README	2008-02-27 19:44:44 UTC (rev 442)
+++ trunk/README	2008-02-27 19:52:54 UTC (rev 443)
@@ -4,6 +4,7 @@
  - Kernel version requirements
  - Supported machines
  - Using pommed
+ - Beeper feature
  - Using gpomme and wmpomme
 
 
@@ -65,9 +66,34 @@
 Using pommed
 ------------
 
-Launch pommed at startup, a simple init script will do.
+Launch pommed at startup, a simple init script will do. Your distribution
+should take care of this.
 
 
+Beeper feature
+--------------
+
+The beeper feature relies on the uinput kernel module being loaded. You can
+check for its availability by checking for the uinput device node, which is
+either one of:
+ - /dev/input/uinput
+ - /dev/uinput
+ - /dev/misc/uinput
+
+Or by checking the output of 
+ $ lsmod | grep uinput
+
+If the module is not loaded, load it manually with
+ # modprobe uinput
+then restart pommed. You'll need to ensure the module is loaded before pommed
+starts; to achieve that, add uinput to /etc/modules.
+
+For the curious, as I've been asked a couple times already: pommed uses the
+uinput facility to create a userspace input device which handles the console
+beep. Once this device is set up, the kernel happily passes down beep events
+to pommed through this device, and pommed only needs to ... well, *beep*.
+
+
 Using gpomme and wmpomme
 ------------------------