For open/openat, if the flags parameter does not contain O_CREAT, the
3rd (variadic) mode_t parameter is irrelevant. Many developers in the past
have passed mode_t (0, 044, 0644, or such), which mig

For open/openat, if the flags parameter does not contain O_CREAT, the
3rd (variadic) mode_t parameter is irrelevant. Many developers in the past
have passed mode_t (0, 044, 0644, or such), which might lead future people
to copy this broken idiom, and perhaps even believe this parameter has some
meaning or implication or application. Delete them all.
This comes out of a conversation where tb@ noticed that a strange (but
intentional) pledge behaviour is to always knock-out high-bits from
mode_t on a number of system calls as a safety factor, and his bewilderment
that this appeared to be happening against valid modes (at least visually),
but no sorry, they are all irrelevant junk. They could all be 0xdeafbeef.
ok millert

show more ...

remove defines for ioctls the kernel doesn't recognise
ok mpi@

Stop writing a pidfile
ok benno jung

Remove function mouse_map. This function is redundant.

ok zhuk@

Now does not need to be initialized event.value.
This not used anymore.

ok deraadt@

Cleanup - remove event WSCONS_EVENT_WSMOUSED_SLEEP, WSCONS_EVENT_WSMOUSED_CLOSE.
Do not need it now.

ok mpi@

Remove mouse.baudrate, it is always 1200.

ok miod@

Remove unused code.

ok miod@

Remove unused variables.

ok miod@

more unsigned char casts for ctype
ok jca

struct timezone is so 1980

delay daemon fork() until after initialisation has completed to fix
rc race that caused X11 to fail to open /dev/wsmouse; ok stsp miod

use timerclear macro

ok miod@

Support mouses with lots of buttons. Also, fix a crash when pressing
a button that's outside of the hardcoded range; miod@ ok

Add the ability to attach wsmoused to a different wsdisplay than wsdisplay0
(i.e. ttyCcfg) with the new -D option.

While there, a lot of cleanup, including not creating a pidfile by default
(since t

Add the ability to attach wsmoused to a different wsdisplay than wsdisplay0
(i.e. ttyCcfg) with the new -D option.

While there, a lot of cleanup, including not creating a pidfile by default
(since there might be more than one wsmoused running on multiple wsdisplay
systems).

show more ...

Since switches from X to consoles are aysnchronous, wsmoused(8) can be awakened
before the X server has release the mouse device. Instead of an arbitrary sleep,
loop (with increasing delays) until we

Since switches from X to consoles are aysnchronous, wsmoused(8) can be awakened
before the X server has release the mouse device. Instead of an arbitrary sleep,
loop (with increasing delays) until we can open the device again.

Found the hard way and tested by jmc@

show more ...

use C99 explicit struct initializer instead of deprecated gcc 2.5
style. ok miod@ millert@

Add support for a fourth axis on wsmouse devices, e.g. on the Apple Might
Mouse. Currently limited to USB mice.

Adapted from a diff from Gareth <garf@loveandnature.co.za> on tech@

setjmp.h not used

prefer a simpler synopsis: we do not really need a separate case for -i;

gcc3 doesn't like varargs, it was found that the varargs.h inclusion is
unnecessary for these files, delete. ok espie@

No need to setup a signal handler for SIGKILL as you can't catch it anyway.

- correct SYNOPSIS
- sort options
- sync usage()
- new sentence, new line

check strdup failure; ok anil millert

try to use the X Window System, X11 or XFree86 consistently.

diffs from Paul Weismann, via mickey@
aided, abetted and ok'd matthieu@