all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Christopher Baines <mail@cbaines.net>
Cc: 25453@debbugs.gnu.org
Subject: bug#25453: Inconsistent keyboard layout affecting encrypted root
Date: Fri, 20 Jan 2017 15:01:36 +0100	[thread overview]
Message-ID: <87vat9akzj.fsf@gnu.org> (raw)
In-Reply-To: <87wpdwzuar.fsf@cbaines.net> (Christopher Baines's message of "Sun, 15 Jan 2017 06:55:24 +0000")

Hi!

Christopher Baines <mail@cbaines.net> skribis:

> I'm using a UK keyboard layout with a computer that I recently installed
> GuixSD on with a encrypted root parition. Immediately after installation
> when I attempted to boot in to the new system for the first time I had
> to enter the passphrase twice, and in doing this, first I had to use the
> keyboard layout under which I carried out the installation (the layout
> which I had intended to use), and then during the early boot stage of
> the system I had to enter the passphrase using a different keyboard
> layout.

Currently installing a keymap is something done by the ‘console-keymap’
Shepherd service, which invokes ‘loadkeys’.  That happens after
“cryptsetup --open” has opened your encrypted root device, hence the
problem.

Should we install the keymap right in the initrd, before we’ve mounted
the root partition?  That would require copying the right keymap(s) and
probably ‘loadkeys’ to the initrd, which might make it quite big.

Suggestions?  How do others handle it?

Thanks for your report,
Ludo’.

  reply	other threads:[~2017-01-20 14:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-15  6:55 bug#25453: Inconsistent keyboard layout affecting encrypted root Christopher Baines
2017-01-20 14:01 ` Ludovic Courtès [this message]
2018-01-14 13:22   ` Mathieu Lirzin
2018-01-17  7:05   ` Chris Marusich
2018-01-17  8:29   ` ng0
2019-03-24 22:21   ` Ludovic Courtès
2019-03-25  5:44     ` Christopher Baines

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87vat9akzj.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=25453@debbugs.gnu.org \
    --cc=mail@cbaines.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.