Date: Mon, 24 Jun 1996 09:25:49 +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, current@freebsd.org Subject: Re: moused not works from rc.i386, but works from command line Message-ID: <199606240725.JAA05329@ra.dkuug.dk> In-Reply-To: <199606232240.CAA00196@nagual.ru> from "=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?=" at Jun 24, 96 02:40:02 am
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:
>
> Steps:
> 1) Start moused from rc.i386
> 2) After login say "vidcontrol -m on"
> You'll see mouse cursor ALWAYS at 0,0 :-(
> When moused killed and restarted from command line,
> all appearse OK.
I'm not sure I understand exactly what you mean here. But anyhow
behavior in this area is very likely to change when I commit the
next generation of this stuff shortly. The protocol between
moused and syscons and eventual other apps, has to change for it
to work proberly. What we have now is only usable to use the
cut&paste functionality, and I wanted the bugs in the generic
mousepointer code shaked out before jumping into deep water...
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
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?199606240725.JAA05329>