Date: Mon, 24 Jun 1996 13:08:09 +0200 (MET DST) From: sos@freebsd.org To: ache@nagual.ru (=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?=) Cc: sos@freebsd.org, andreas@klemm.gtn.com, current@freebsd.org Subject: Re: Syscons CUT&PASTE functionality added... Message-ID: <199606241108.NAA06723@ra.dkuug.dk> In-Reply-To: <199606241035.OAA00424@nagual.ru> from "=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?=" at Jun 24, 96 02:35:36 pm
next in thread | previous in thread | raw e-mail | index | archive | help
In reply to =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= who wrote:
>
> > The problem here is that the vty's aren't there when before the
> > getty's are run. THe vty are dynamically allocated (to save space)
> > and so they are actually not there before they are opened the first
> > time (by the getty). This apparently effects the way the mousepointer
> > is handled. Oh well, I'll look at it...
>
> You need some protocol talking back: syscons -> moused
> It needed in following cases at least:
NO WAY! it would be the ugliest hack I could think of solving this..
> 1) New tty allocated (by getty): syscons tells previously running
> moused to handle it.
>
> [it fix starting from rc bug]
moused should have absolutely NO knowledge of what goes on on the
display, its only mission in life is to interpret mouse movement
codes.
> 2) Graphics mode entered: syscons tells moused to close
> mouse device.
> 3) Graphics mode exited: syscons tells moused to open
> mouse device.
>
> [it fix X11 conflicts]
Nope, because X NEVER closes the mouse device :(
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Soren Schmidt (sos@FreeBSD.org) FreeBSD Core Team
So much code to hack -- so little time.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199606241108.NAA06723>