From owner-freebsd-hackers@FreeBSD.ORG Tue Aug 19 08:28:01 2014 Return-Path: Delivered-To: freebsd-hackers@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 EF2327FF; Tue, 19 Aug 2014 08:28:01 +0000 (UTC) Received: from mailout04.t-online.de (mailout04.t-online.de [194.25.134.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mailout00.t-online.de", Issuer "TeleSec ServerPass DE-1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B29DD3F1A; Tue, 19 Aug 2014 08:28:01 +0000 (UTC) Received: from fwd23.aul.t-online.de (fwd23.aul.t-online.de [172.20.26.128]) by mailout04.t-online.de (Postfix) with SMTP id AAA034CF6AD; Tue, 19 Aug 2014 10:27:53 +0200 (CEST) Received: from [192.168.119.33] (bdQ70BZXwhNaqXRtkKkizbk0kgCi-rTf20WyjAHJeW+PfPM82RcMk8CMlVyq8QZgbf@[84.154.101.219]) by fwd23.t-online.de with (TLSv1.2:ECDHE-RSA-AES256-SHA encrypted) esmtp id 1XJeli-0vTDk00; Tue, 19 Aug 2014 10:27:50 +0200 Message-ID: <53F30A81.9090302@freebsd.org> Date: Tue, 19 Aug 2014 10:27:45 +0200 From: Stefan Esser User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.0 MIME-Version: 1.0 To: "freebsd-hackers@freebsd.org" Subject: Opinions thought regarding: NEWCONS, rc.conf and rc.d/syscons Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-ID: bdQ70BZXwhNaqXRtkKkizbk0kgCi-rTf20WyjAHJeW+PfPM82RcMk8CMlVyq8QZgbf X-TOI-MSGID: 092e91f1-6af2-4cd4-9e92-2bfa06e4a29b X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Aug 2014 08:28:02 -0000 As you all probably know, 10.1 will ship with both SYSCONS and NEWCONS. I'm working keymap files for NEWCONS (translated from those in SYSCONS), and they'll need to be named differently than before. The SYSCONF keymap names in rc.conf will not work for NEWCONS. They include an encoding scheme in their name, while NEWCONS universally uses Unicode. There are a few points that still need to be considered for 10.1: a) Is rc.d/syscons still an appropriate name when using NEWCONS? (I'd leave it unchanged, but I thought I'd ask ...) b) Do we need to identify NEWCONS vs. SYSCONS in the messages printed by that rc script? (I guess this might be a good idea.) c) Do we expect to warn the user when he has a SYSCONS keymap name specified in the rc.conf "keymap" variable, while using NEWCONS? (This might be a good idea, at least when the default is to use NEWCONS and the user might not be aware of the change.) d) Do we want to provide the user with an information regarding the name of the SYSCONS keymap configured, to ease the transition? (Could be done ...) e) Do we want the rc script to translate the SYSCONS keymap name to its new form? (This might be good for people using foreign keyboards, if their password uses characters located at other positions than on the default keymap, that will be used if no valid "keymap" is specified.) f) It might be good to introduce "keymap_sc" (and/or "keymap_vt") as a value used in preference to "keymap" if defined and the corresponding console driver is detected. (An alternativ to e) that is easier to implement and still allows to have one rc.conf file that covers both SYSCONS and NEWCONS.) I'd appreciate opinios and ideas how to proceed with these questions. Regards, STefan