From owner-freebsd-arch@FreeBSD.ORG Mon Dec 12 07:52:57 2011 Return-Path: Delivered-To: arch@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C616A1065673; Mon, 12 Dec 2011 07:52:57 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id E08508FC0A; Mon, 12 Dec 2011 07:52:56 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id JAA14892; Mon, 12 Dec 2011 09:52:53 +0200 (EET) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1Ra0gv-000HyJ-K2; Mon, 12 Dec 2011 09:52:53 +0200 Message-ID: <4EE5B2D4.9050705@FreeBSD.org> Date: Mon, 12 Dec 2011 09:52:52 +0200 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:8.0) Gecko/20111206 Thunderbird/8.0 MIME-Version: 1.0 To: Alexander Yerenkow References: <4EE52469.3050201@FreeBSD.org> In-Reply-To: X-Enigmail-Version: undefined Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: arch@FreeBSD.org, FreeBSD current Subject: Re: grabbing console (syscons) in kernel X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Dec 2011 07:52:57 -0000 on 12/12/2011 00:06 Alexander Yerenkow said the following: > > > 2011/12/11 Andriy Gapon > > > > There are a few cases when the kernel needs to interact with a user via syscons. > This is the cases where the kernel not only spews some output but also expects > some input. Some examples are: > - asking for a root filesystem specification > - entering ddb > - asking to press a key for reboot > > In this cases the kernel implicitly grabs the console for its own use. > I'd like to make action more explicit. > > What do you think about the approach and implementation in the following > patches? > Thank you! > > https://gitorious.org/~avg/freebsd/avgbsd/commit/5248b49ebf84d98a0597fa5aa4d813a38f581acc > https://gitorious.org/~avg/freebsd/avgbsd/commit/a0849c52242378474bb2eaa41726376fbc4c5bf6 > https://gitorious.org/~avg/freebsd/avgbsd/commit/a67515cbd720b16f03ba435ed182966a8a338b15 > https://gitorious.org/~avg/freebsd/avgbsd/commit/b8864b68b4c0e26ece065a38301c305833be32eb > https://gitorious.org/~avg/freebsd/avgbsd/commit/1017ae425d8abecd7482bd6c6deaaf9f25f5c6cd > > P.S. one of the benefits is that a keyboard is put into and out of the polling > mode before getting all the required input and after that; not around each > character as it is done now in rather twisted way. > > > Does asking for geli password is such case too? Yes. > For example, I have mouse, which can disappear/reappear while laying still; and > when geli asks password, ums0 connect message can appear, which moves line > "Please enter geli password..." to top, and it can be missed; > This behavior somehow change? No. The patches do not contain user-visible changes. They make things easier for keyboard drivers and hopefully provide a more logical interface to kernel. Their primary target is the input path, they do not introduce any changes to the output path. -- Andriy Gapon