From owner-freebsd-current Mon Jun 24 02:14:28 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA08541 for current-outgoing; Mon, 24 Jun 1996 02:14:28 -0700 (PDT) Received: from ra.dkuug.dk (ra.dkuug.dk [193.88.44.193]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id CAA08536 for ; Mon, 24 Jun 1996 02:14:23 -0700 (PDT) Received: (from sos@localhost) by ra.dkuug.dk (8.6.12/8.6.12) id LAA06110; Mon, 24 Jun 1996 11:14:06 +0200 Message-Id: <199606240914.LAA06110@ra.dkuug.dk> Subject: Re: moused conflicts with X11 To: msmith@atrad.adelaide.edu.au (Michael Smith) Date: Mon, 24 Jun 1996 11:14:06 +0200 (MET DST) Cc: current@freebsd.org (FreeBSD current) In-Reply-To: <199606240851.SAA21550@genesis.atrad.adelaide.edu.au> from "Michael Smith" at Jun 24, 96 06:21:48 pm From: sos@freebsd.org Reply-to: sos@freebsd.org X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In reply to Michael Smith who wrote: > > Either we need a 'mouse' line discipline that allows multiple readers > (erk.), or we look at something like the 'snp' device's hooks to provide > moused with a means of watching the mouse without interfering with the > X server. Ahhh, how does this snp thingy work ?? (I'm too lazy to look in the sources) Could it be used to snoop the bytestream from the "known" mousedevice ?? If so, that would be neat to have, just config the mousedev to syscons via an ioctl, and there we go.... no moused no nothing (except that I now need to make this a lkm due to the amount of code in syscons).... > I don't think we can afford to change what the X server sees, and I don't > like the way the Linux folks did it (their mouse daemon is basically a pipe). My wiev exactly.. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Soren Schmidt (sos@FreeBSD.org) FreeBSD Core Team So much code to hack -- so little time.