From owner-freebsd-current  Mon Jun 24 23:58:58 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id XAA22843
          for current-outgoing; Mon, 24 Jun 1996 23:58:58 -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 XAA22836;
          Mon, 24 Jun 1996 23:58:55 -0700 (PDT)
Received: (from sos@localhost) by ra.dkuug.dk (8.6.12/8.6.12) id IAA15097; Tue, 25 Jun 1996 08:58:43 +0200
Message-Id: <199606250658.IAA15097@ra.dkuug.dk>
Subject: Re: moused conflicts with X11
To: dawes@rf900.physics.usyd.edu.au (David Dawes)
Date: Tue, 25 Jun 1996 08:58:42 +0200 (MET DST)
Cc: sos@freebsd.org, current@freebsd.org
In-Reply-To: <199606250109.LAA02494@rf900.physics.usyd.edu.au> from "David Dawes" at Jun 25, 96 11:09:25 am
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 David Dawes who wrote:
> 
> >Because the way I understand it, its because BOTH mosed & X has the
> >mousedevice open at the same time, this is only fixable by having
> >one of then close it. BUT the X server NEVER closes it during its
> >life time :(
> 
> That isn't true for the XFree86 servers.  They close the mouse device
> when switching away from the X server.  They do this so that other things
> can use the mouse (eg, an X server running on another vty).

Great !, thanks for the enlightment, it has to be my old'ish Xaccel
server that does wierd things. Now that I have your attention, how
would you guys prefer to talk to the mouse ??

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Soren Schmidt             (sos@FreeBSD.org)             FreeBSD Core Team
               So much code to hack -- so little time.