aboutsummaryrefslogtreecommitdiff
path: root/marsond.rst
diff options
context:
space:
mode:
Diffstat (limited to 'marsond.rst')
-rw-r--r--marsond.rst25
1 files changed, 25 insertions, 0 deletions
diff --git a/marsond.rst b/marsond.rst
index 8f56ace..2a95b71 100644
--- a/marsond.rst
+++ b/marsond.rst
@@ -57,6 +57,15 @@ does, with SDL 1 and 2 running under X (and SDL 1 on the console,
too). I don't use Wayland, so I haven't tested it there. If you do,
please contact me and let me know if it works for you.
+For normal use, **marsond** will be started by a **udev**\(7) rule
+when the adaptor is plugged in (including booting with the adaptor
+connected). The udev rule is found in:
+
+ /etc/udev/rules.d/99-marsond.rules
+
+...which can be edited to change the options it's run with, if
+needed. The defaults work well on the author's system.
+
**marsond** must be run as root. At startup, it does these
things as root:
@@ -137,6 +146,22 @@ MARSOND_GROUP
the primary group of the user it's running as. Normally
you won't have to set this.
+LIMITATIONS
+===========
+
+Only one MT-606-1 device is supported, out of the box. This shouldn't
+really be a problem (do you really need 2 keyboards?) but it's worth
+mentioning. If you really do own two of these adaptors and want to use
+them on the same PC, you could add a second udev rule (with -k option
+for the daemon).
+
+This isn't really a **marsond** problem per se, but when Xorg detects
+a new keyboard, it resets your keyboard repeat rate (**xset r**)
+and custom keymap (**xmodmap**\(1)). If you use a 'desktop' such
+as KDE, GNOME, or XFCE, it should re-apply your settings. For a
+traditional window manager (WindowMaker, FVWM2, etc), this can be very
+annoying.
+
.. EXIT STATUS
.. ===========