From owner-freebsd-current@FreeBSD.ORG Mon May 12 23:51:29 2014 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 56D263EE for ; Mon, 12 May 2014 23:51:29 +0000 (UTC) Received: from mailhost.m5p.com (ip-2-1-0-2.r03.asbnva02.us.ce.gin.ntt.net [IPv6:2001:418:0:5000::16]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 15A52239D for ; Mon, 12 May 2014 23:51:28 +0000 (UTC) Received: from wonderland.m5p.com (localhost [IPv6:::1]) by mailhost.m5p.com (8.14.5/8.14.5) with ESMTP id s4CNpLRu022834 for ; Mon, 12 May 2014 19:51:26 -0400 (EDT) (envelope-from george+freebsd@m5p.com) Message-ID: <53715E79.2040408@m5p.com> Date: Mon, 12 May 2014 19:51:21 -0400 From: George Mitchell User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Re: RFT vidcontrol for vt(4) References: <20140311162743.072870a9afd4f74fff9e99e8@ddteam.net> <5370CE34.8000905@orange.fr> <20140512171415.558dbcb68971d1db675ea39e@ddteam.net> <5370E47E.7030304@orange.fr> <5370E800.8040803@freebsd.org> In-Reply-To: <5370E800.8040803@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.73 on 10.100.0.3 X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.7 (mailhost.m5p.com [IPv6:::1]); Mon, 12 May 2014 19:51:26 -0400 (EDT) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18 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: Mon, 12 May 2014 23:51:29 -0000 On 05/12/14 11:25, Nathan Whitehorn wrote: > [...] > > Is there any reason not to have kbdmux be mandatory at this point? > [...] Does this mean mandatory in the sense that the kbdmux driver always gets built and loaded, or that the kbdmux driver must always be in operation (treating all keyboard-like devices as a single unified source of keystrokes)? I could live with the first, but there are definitely times that I want multiple independent keyboards on a system to be considered unrelated to one another. -- George