From owner-freebsd-stable Tue May 27 12:55:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA00867 for stable-outgoing; Tue, 27 May 1997 12:55:07 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA00860 for ; Tue, 27 May 1997 12:55:04 -0700 (PDT) Received: from localhost (tom@localhost) by misery.sdf.com (8.8.5/8.8.5) with SMTP id MAA06917 for ; Tue, 27 May 1997 12:52:35 -0700 (PDT) X-Authentication-Warning: misery.sdf.com: tom owned process doing -bs Date: Tue, 27 May 1997 12:52:33 -0700 (PDT) From: Tom Samplonius To: freebsd-stable@freebsd.org Subject: moused & mouse pointer in 2.2-stable Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Is it just me, or does the mouse console pointer not work worth a damn? I use "vidcontrol -m on" to turn the pointer on, on a couple of the virtual consoles, and all seems well, but within a couple of hours the pointer disappears off of all the consoles. "vidcontrol -m on" has no effect. Re-booting the machine gets the pointer working again. Also, shouldn't the /etc/sysconfig or /etc/rc.conf stuff run "vidcontrol -m on" for every virtual console if moused is started? What's the point of auto starting moused, if you aren't going to turn on the mouse pointer on? Tom