From owner-freebsd-current@FreeBSD.ORG Thu Jan 4 00:03:42 2007 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5045F16A416; Thu, 4 Jan 2007 00:03:42 +0000 (UTC) (envelope-from maksim.yevmenkin@savvis.net) Received: from mailgate1b.savvis.net (mailgate1b.savvis.net [216.91.182.6]) by mx1.freebsd.org (Postfix) with ESMTP id 0E1CE13C457; Thu, 4 Jan 2007 00:03:42 +0000 (UTC) (envelope-from maksim.yevmenkin@savvis.net) Received: from localhost (localhost.localdomain [127.0.0.1]) by mailgate1b.savvis.net (Postfix) with ESMTP id 490C73BF39; Wed, 3 Jan 2007 17:45:32 -0600 (CST) Received: from mailgate1b.savvis.net ([127.0.0.1]) by localhost (mailgate1b.savvis.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 30781-01-4; Wed, 3 Jan 2007 17:45:32 -0600 (CST) Received: from [10.12.163.251] (unknown [10.12.163.251]) by mailgate1b.savvis.net (Postfix) with ESMTP id D3BED3BF35; Wed, 3 Jan 2007 17:45:31 -0600 (CST) Message-ID: <459C401B.20005@savvis.net> Date: Wed, 03 Jan 2007 15:45:31 -0800 From: Maksim Yevmenkin User-Agent: Thunderbird 1.5.0.5 (X11/20060906) MIME-Version: 1.0 To: John Baldwin References: <459B5CA9.4070909@root.org> <20070103124106.U82671@maildrop.int.zabbadoz.net> <20070103223621.GX78631@wantadilla.lemis.com> <200701031758.31576.jhb@freebsd.org> In-Reply-To: <200701031758.31576.jhb@freebsd.org> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at savvis.net Cc: Greg 'groggy' Lehey , current@freebsd.org Subject: Re: How to resolve problems in our software X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Jan 2007 00:03:42 -0000 John Baldwin wrote: > [ moved to current@ ] > > On Wednesday 03 January 2007 17:36, Greg 'groggy' Lehey wrote: >> So: we have a problem with kbdmux, which looks suspiciously like a >> bug. I don't know this code, but it seems to have been there for a >> while. How, in your opinion, do I go about fixing it? > > So it's not clear from your original message how you are using kbdcontrol and > kbdmux. It sounds like you want the USB keyboard (when present) to be the > normal keyboard for syscons and atkbd0 to be left alone for use by a specific > process, yes? Can't you just do 'kbdcontrol -A atkbd0 < /dev/kbdmux0' once not /dev/kbdmux0 - it is a keyboard device (just like /dev/ukb0 and /dev/atkbd0) and it will be busy because syscons already got kbdmux as its main keyboard. please use < /dev/console or < /dev/ttyv0. > during boot and be done? The default for the USB keyboard should be for it > to be added to kbdmux0 and thus result in it being used for the regular > console without any special magic needed. other then above comment everything else is correct and i suggested the same in private email. thanks, max