Date: 08 Feb 1997 01:51:01 -0600 From: Zach Heilig <zach@blizzard.gaffaneys.com> To: David Nugent <davidn@labs.usn.blaze.net.au> Cc: Leonard Chua <lenc@earth.infinetconsulting.com>, freebsd-bugs@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: moused and X11R6 Message-ID: <87bu9venx6.fsf@murkwood.gaffaneys.com> In-Reply-To: David Nugent's message of Sat, 8 Feb 1997 16:55:55 %2B1100 References: <876804rsia.fsf@murkwood.gaffaneys.com> <Pine.BSF.3.95.970207222919.2151A-100000@chaos.ecpnet.com> <19970208165555.12961@usn.blaze.net.au>
next in thread | previous in thread | raw e-mail | index | archive | help
David Nugent <davidn@labs.usn.blaze.net.au> writes: > It would appear that you've configured both X and moused to > access the mouse directly, in which case they're fighting for > control, and certainly you'll see the results that you've > observed. Nope, moused used /dev/cuaa0, X used /dev/sysmouse. What are the device numbers on /dev/sysmouse supposed to be? I have: crw-rw---- 1 uucp dialer 28, 128 Feb 8 01:35 /dev/cuaa0 crw------- 1 root wheel 12, 128 Feb 8 00:58 /dev/sysmouse I killed moused, and set the X mouse pointer to /dev/cuaa0. The problem seems to have gone away. Either the above permissions are wrong, or moused is mildly broken. -- Zach Heilig (zach@blizzard.gaffaneys.com) | ALL unsolicited commercial email Support bacteria -- it's the only | is unwelcome. I avoid dealing form of culture some people have! | with companies that email ads.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?87bu9venx6.fsf>