Date: Wed, 16 Dec 2015 15:56:48 +0100 (CET) From: =?ISO-8859-1?Q?Trond_Endrest=F8l?= <Trond.Endrestol@fagskolen.gjovik.no> To: Carsten Kunze <carsten.kunze@arcor.de> Cc: freebsd-current@freebsd.org Subject: Re: keymap set after file system decryption Message-ID: <alpine.BSF.2.20.1512161545400.1026@mail.fig.ol.no> In-Reply-To: <37578766.236860.1450260266870.JavaMail.ngmail@webmail18.arcor-online.net> References: <37578766.236860.1450260266870.JavaMail.ngmail@webmail18.arcor-online.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 16 Dec 2015 11:04+0100, Carsten Kunze wrote:
> Hello,
>
> according to the boot messages the keymap is set after decryption of
> file systems. I consider this as a bug. The geli decryption script
> asks for the passphrase which can't of course be input if the kaymap
> is not set.
>
> Handbook §17.12 does not mention the keymap setup. What can I do to
> make this work? (Of course I can call e.g. kbdmap in
> /etc/rc.d/geli, but this is kind of tinkering.)
I guess we who live outside the US should take into account that PCs
are initialised by firmware to the US keyboard layout and the 437 code
page, courtesy of IBM, 1981.
I'm not sure if the creators of (U)EFI has considered other keyboard
layouts and/or code pages at boot time.
A bad workaround is to copy the suitable keymap from /usr/share... to
/etc, along with /usr/sbin/kbdcontrol, and add a suitable line to one
or either of /etc/rc.d/geli{,2}, e.g.:
/etc/kbdcontrol -l /etc/german.iso.kbd
kbdcontrol is linked only to libc:
$ ldd `which kbdcontrol`
/usr/sbin/kbdcontrol:
libc.so.7 => /lib/libc.so.7 (0x800827000)
--
+-------------------------------+------------------------------------+
| Vennlig hilsen, | Best regards, |
| Trond Endrestøl, | Trond Endrestøl, |
| IT-ansvarlig, | System administrator, |
| Fagskolen Innlandet, | Gjøvik Technical College, Norway, |
| tlf. mob. 952 62 567, | Cellular...: +47 952 62 567, |
| sentralbord 61 14 54 00. | Switchboard: +47 61 14 54 00. |
+-------------------------------+------------------------------------+
From owner-freebsd-current@freebsd.org Wed Dec 16 15:17:17 2015
Return-Path: <owner-freebsd-current@freebsd.org>
Delivered-To: freebsd-current@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
[IPv6:2001:1900:2254:206a::19:1])
by mailman.ysv.freebsd.org (Postfix) with ESMTP id 66625A4816C
for <freebsd-current@mailman.ysv.freebsd.org>;
Wed, 16 Dec 2015 15:17:17 +0000 (UTC)
(envelope-from freebsd-listen@fabiankeil.de)
Received: from smtprelay05.ispgateway.de (smtprelay05.ispgateway.de
[80.67.31.98])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(Client did not present a certificate)
by mx1.freebsd.org (Postfix) with ESMTPS id 2B3D012AA
for <freebsd-current@freebsd.org>; Wed, 16 Dec 2015 15:17:16 +0000 (UTC)
(envelope-from freebsd-listen@fabiankeil.de)
Received: from [78.35.181.63] (helo=fabiankeil.de)
by smtprelay05.ispgateway.de with esmtpsa (TLSv1.2:AES128-GCM-SHA256:128)
(Exim 4.84) (envelope-from <freebsd-listen@fabiankeil.de>)
id 1a9Di2-0005E6-T9; Wed, 16 Dec 2015 16:09:42 +0100
Date: Wed, 16 Dec 2015 16:08:54 +0100
From: Fabian Keil <freebsd-listen@fabiankeil.de>
To: Oliver Pinter <oliver.pinter@hardenedbsd.org>
Cc: FreeBSD Current <freebsd-current@freebsd.org>
Subject: Re: fork_findpid() - Fatal trap 12: page fault while in kernel mode
Message-ID: <20151216160854.29138e1b@fabiankeil.de>
In-Reply-To: <CAPQ4ffto90V42OEZ1CoY_CtQKvkn7KDtkULfb1Lhi-podew_AA@mail.gmail.com>
References: <20151215174238.2d7cc3bb@fabiankeil.de>
<20151215192016.GC73098@mutt-hardenedbsd>
<CAPQ4ffu3TZJGq=+JLmwPvds-y6p904-GdPZJ=uQ-vWb8poU=qQ@mail.gmail.com>
<20151216131621.42a0d97e@fabiankeil.de>
<CAPQ4ffto90V42OEZ1CoY_CtQKvkn7KDtkULfb1Lhi-podew_AA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
boundary="Sig_/4xBt5RJy+4p7sii6cQDkXXF"; protocol="application/pgp-signature"
X-Df-Sender: Nzc1MDY3
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>;
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Dec 2015 15:17:17 -0000
--Sig_/4xBt5RJy+4p7sii6cQDkXXF
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable
Oliver Pinter <oliver.pinter@hardenedbsd.org> wrote:
> Yes, it's a HardenedBSD commit. Currently only a workaround, because I ha=
ve
> now lesser time for the real fix in this month.
>=20
> Are you running on ZFS?
Yes.
Fabian
--Sig_/4xBt5RJy+4p7sii6cQDkXXF
Content-Type: application/pgp-signature
Content-Description: OpenPGP digital signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iEYEARECAAYFAlZxfoYACgkQBYqIVf93VJ1iRwCgywNRJNo7TfpWkLSwPQBU1dr+
7EwAniwrVU+0fnaTFpdY0m4jl6FUkDWY
=RVwZ
-----END PGP SIGNATURE-----
--Sig_/4xBt5RJy+4p7sii6cQDkXXF--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.20.1512161545400.1026>