From owner-freebsd-current  Mon Jun 24 18:09:38 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id SAA28974
          for current-outgoing; Mon, 24 Jun 1996 18:09:38 -0700 (PDT)
Received: from rf900.physics.usyd.edu.au (rf900.physics.usyd.edu.au [129.78.129.109])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id SAA28957;
          Mon, 24 Jun 1996 18:09:33 -0700 (PDT)
Received: (from dawes@localhost) by rf900.physics.usyd.edu.au (8.6.11/8.6.9) id LAA02494; Tue, 25 Jun 1996 11:09:25 +1000
From: David Dawes <dawes@rf900.physics.usyd.edu.au>
Message-Id: <199606250109.LAA02494@rf900.physics.usyd.edu.au>
Subject: Re: moused conflicts with X11
To: sos@freebsd.org
Date: Tue, 25 Jun 1996 11:09:25 +1000 (EST)
Cc: current@freebsd.org
In-Reply-To: <199606241104.NAA06679@ra.dkuug.dk> from "sos@freebsd.org" at Jun 24, 96 01:04:18 pm
X-Mailer: ELM [version 2.4 PL23]
Content-Type: text
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>> > Actually I think its an artifact from both moused & the X server
>> > having /dev/mousedev open at the same time. This is only
>> > fixable by either killing moused when running X, or have
>> > moused track the shown vty, and open/close /dev/mousedev according
>> > to that.
>> 
>> Why? Syscons already detect when terminal video mode
>> changed to graphics mode. All you need is turn off moused
>> while syscons in graphics mode and turn it back on
>> graphics mode exit.
>
>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).

David