DragonFly BSD
DragonFly bugs List (threaded) for 2004-04
[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]

Re: New vidcontrol moused error messages

From: Sascha Wildner <saw@xxxxxxxxx>
Date: Mon, 26 Apr 2004 23:12:05 +0200

Matthew Dillon wrote:

> I think we should make one minor change to the code, and that is to
> deal with the case where the system boots up on a serial console.
> The vidcontrol line should probably be:
> vidcontrol ${_mousechar_arg} -m on < /dev/ttyv0
> If you test that out and make sure it still works as advertised, I'll
> commit it.


I tested it and the mouse pointer is visible on all my vtys and there are no error messages anymore.

I didn't test serial behavior (I don't have a serial console).

Also, I didn't quite understand the meaning of the 'vidcontrol -M' option (or mousechar_start in rc.conf). Regardless of what I set it to, there is no noticeable effect...



*** /usr/src/etc/rc.d/moused	Tue Jan 27 01:42:45 2004
--- /usr/s/src/etc/rc.d/moused	Mon Apr 26 22:58:06 2004
*** 31,39 ****

! 	for ttyv in /dev/ttyv* ; do
! 		vidcontrol < ${ttyv} ${_mousechar_arg} -m on
! 	done
  	echo '.'

--- 31,38 ----

! 	vidcontrol ${_mousechar_arg} -m on < /dev/ttyv0
  	echo '.'

[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]