From owner-freebsd-current@FreeBSD.ORG Wed Jan 3 23:22:28 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 155AD16A412 for ; Wed, 3 Jan 2007 23:22:28 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by mx1.freebsd.org (Postfix) with ESMTP id B9E3113C44C for ; Wed, 3 Jan 2007 23:22:27 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from localhost.corp.yahoo.com (john@localhost [127.0.0.1]) (authenticated bits=0) by server.baldwin.cx (8.13.6/8.13.6) with ESMTP id l03MwKw6023878; Wed, 3 Jan 2007 17:58:22 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: "Greg 'groggy' Lehey" Date: Wed, 3 Jan 2007 17:58:31 -0500 User-Agent: KMail/1.9.1 References: <459B5CA9.4070909@root.org> <20070103124106.U82671@maildrop.int.zabbadoz.net> <20070103223621.GX78631@wantadilla.lemis.com> In-Reply-To: <20070103223621.GX78631@wantadilla.lemis.com> MIME-Version: 1.0 Content-Disposition: inline Message-Id: <200701031758.31576.jhb@freebsd.org> Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [127.0.0.1]); Wed, 03 Jan 2007 17:58:22 -0500 (EST) X-Virus-Scanned: ClamAV 0.88.3/2411/Wed Jan 3 13:04:33 2007 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: current@freebsd.org Subject: Re: How to resolve problems in our software (was: Problems with kbdmux) 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: Wed, 03 Jan 2007 23:22:28 -0000 [ 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 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. -- John Baldwin