Date: Thu, 10 Mar 2005 16:08:19 +0100 From: des@des.no (=?iso-8859-1?q?Dag-Erling_Sm=F8rgrav?=) To: Brooks Davis <brooks@one-eyed-alien.net> Cc: freebsd-usb@freebsd.org Subject: Re: KVM USB Message-ID: <86y8cvsfmk.fsf@xps.des.no> In-Reply-To: <20050309194028.GA17398@odin.ac.hmc.edu> References: <aa8567bf050309111011a8a824@mail.gmail.com> <20050309194028.GA17398@odin.ac.hmc.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
Brooks Davis <brooks@one-eyed-alien.net> writes:
> This is caused by a bug in /etc/devd.conf that I fixed a week ago in 5.
> Just change the line to refer to ukbd0 instead of bogusly refering to
> kbd1. The problem was caused by crappy examples in the manpage making
> me think you had to use the generic /dev/kbd# device not the specific
> /dev/ukdb# device with kbdcontrol.
It's still wrong. At the very least, the attach trigger should be
changed to
attach 100 {
device-name "ukbd[0-9]+";
action "kbdcontrol -k /dev/$device-name < /dev/console";
};
but actually there is no way devd can get it right in the general
case, because there's no correct answer to what to do on detach.
The correct solution would be to teach kbd to multiplex keyboards,
like scmouse multiplexes mice.
DES
--=20
Dag-Erling Sm=F8rgrav - des@des.no
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86y8cvsfmk.fsf>