SlackBuildsOrg/accessibility/ydotool
B. Watson 4003242c76
accessibility/ydotool: Updated for version 1.0.4.
Signed-off-by: B. Watson <urchlay@slackware.uk>

Signed-off-by: Willy Sudiarto Raharjo <willysr@slackbuilds.org>
2023-07-15 17:30:14 +07:00
..
project_version.diff
README accessibility/ydotool: Updated for version 1.0.4. 2023-07-15 17:30:14 +07:00
slack-desc
ydotool.1 accessibility/ydotool: Updated for version 1.0.4. 2023-07-15 17:30:14 +07:00
ydotool.info accessibility/ydotool: Updated for version 1.0.4. 2023-07-15 17:30:14 +07:00
ydotool.SlackBuild accessibility/ydotool: Updated for version 1.0.4. 2023-07-15 17:30:14 +07:00
ydotoold.8 accessibility/ydotool: Updated for version 1.0.4. 2023-07-15 17:30:14 +07:00

ydotool (send fake keyboard/mouse events to the kernel)

ydotool is an automation tool, similar to xdotool, but it doesn't
require X. It can be used to send input to console or wayland
applications, as well as X.

ydotool works differently from xdotool. xdotool sends X events
directly to X server, while ydotool uses the uinput framework of Linux
kernel to emulate an input device.

To use ydotool, the user must have read/write access to /dev/uinput.
On Slackware, this means ydotool would need root access. This
SlackBuild installs ydotool setuid root, but only users in the
'console' group can run it. Since 'console' users can already use the
real keyboard and mouse, it doesn't seem like a huge security risk to
let them send fake events. If this bothers you, run the script with
SETUID=no in the environment to disable it.

ydotool also requires its daemon (ydotoold) to be running. It can be
started manually, or you could start it from /etc/rc.d/rc.local with
code like this:

if [ -x /usr/sbin/ydotoold ]; then
  /usr/sbin/ydotoold &> /var/log/ydotoold/log &
fi