From owner-freebsd-current@FreeBSD.ORG Wed Feb 13 20:56:46 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id DA93D430 for ; Wed, 13 Feb 2013 20:56:46 +0000 (UTC) (envelope-from marius@alchemy.franken.de) Received: from alchemy.franken.de (alchemy.franken.de [194.94.249.214]) by mx1.freebsd.org (Postfix) with ESMTP id 61E15EC0 for ; Wed, 13 Feb 2013 20:56:46 +0000 (UTC) Received: from alchemy.franken.de (localhost [127.0.0.1]) by alchemy.franken.de (8.14.5/8.14.5/ALCHEMY.FRANKEN.DE) with ESMTP id r1DKuf8J062364; Wed, 13 Feb 2013 21:56:41 +0100 (CET) (envelope-from marius@alchemy.franken.de) Received: (from marius@localhost) by alchemy.franken.de (8.14.5/8.14.5/Submit) id r1DKuf0Q062363; Wed, 13 Feb 2013 21:56:41 +0100 (CET) (envelope-from marius) Date: Wed, 13 Feb 2013 21:56:41 +0100 From: Marius Strobl To: Hans Petter Selasky Subject: Re: [RFC] USB keyboard and devd.conf Message-ID: <20130213205641.GK80850@alchemy.franken.de> References: <201302111343.29568.hselasky@c2i.net> <20130212145100.GA29324@alchemy.franken.de> <201302130923.25087.hselasky@c2i.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201302130923.25087.hselasky@c2i.net> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 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, 13 Feb 2013 20:56:46 -0000 On Wed, Feb 13, 2013 at 09:23:25AM +0100, Hans Petter Selasky wrote: > On Tuesday 12 February 2013 15:51:01 Marius Strobl wrote: > > On Mon, Feb 11, 2013 at 01:43:29PM +0100, Hans Petter Selasky wrote: > > > Hi, > > > > > > Does anyone need these lines in /etc/devd.conf ? > > > > > > === etc/devd.conf > > > ================================================================== > > > --- etc/devd.conf (revision 246620) > > > +++ etc/devd.conf (local) > > > @@ -105,16 +105,6 @@ > > > > > > # action "sleep 2 && /usr/sbin/ath3kfw -d $device-name -f > > > /usr/local/etc/ath3k-1.fw"; #}; > > > > > > -# When a USB keyboard arrives, attach it as the console keyboard. > > > -attach 100 { > > > - device-name "ukbd0"; > > > - action "/etc/rc.d/syscons setkeyboard /dev/ukbd0"; > > > -}; > > > -detach 100 { > > > - device-name "ukbd0"; > > > - action "/etc/rc.d/syscons setkeyboard /dev/kbd0"; > > > -}; > > > - > > > > > > notify 100 { > > > > > > match "system" "DEVFS"; > > > match "subsystem" "CDEV"; > > > > > > I plan to remove the lines marked with minus, because we now have kbdmux. > > > > Do these entries have negative impact on systems using kbdmux(4)? > > Will their lack have impact on systems not using kbdmux(4)? I typically > > remove or at least disable the latter on machines without atkbd(4) etc. > > hardware and thus ukbd(4) is the only keyboard driver ever used there. > > > > Hi, > > I suspect a system without kbdmux will still need these. However, these lines > are not correct with regard to multiple USB keyboards. > Yes, but do these lines have ill effects for configurations with kbdmux(4) and multiple keyboards? If not then I'd strongly suggest to keep them for the sake of making configurations without kbdmux(4) work out of the box. If yes, I'd at least keep them in a commented out form and add a mark saying that these are required without kbdmux(4). Marius