mkinitrd unification across distributions
 help / color / mirror / Atom feed
From: Harald Hoyer <harald-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Andrey Borzenkov <arvidjaar-JGs/UdohzUI@public.gmane.org>
Cc: initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	aidecoe-2qtfh70TtYba5EbDDlwbIw@public.gmane.org
Subject: Re: [PATCH] Fix autodetection of UNICODE keymap
Date: Thu, 12 Aug 2010 13:08:25 +0200	[thread overview]
Message-ID: <4C63D629.4040204@redhat.com> (raw)
In-Reply-To: <4C63D565.3030405-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>

On 08/12/2010 01:05 PM, Harald Hoyer wrote:
> On 08/11/2010 07:47 PM, Andrey Borzenkov wrote:
>> +
>> + # KEYTABLE is a bit special - it defines base keymap name and UNICODE
>> + # determines whether non-UNICODE or UNICODE version is used
>> +
>> + if [[ ${KEYTABLE} ]]; then
>> + if [[ ${UNICODE} == 1 ]]; then
>> + [[ ${KEYTABLE} =~ .*\.uni.* ]] || KEYTABLE=${KEYTABLE%.map*}.uni
>> + fi
>> +
>> + KEYMAP=${KEYTABLE}
>> + fi
>
> On Fedora we would end with:
>
> KEYTABLE="de-latin1-nodeadkeys"
>
> at
>
> KEYMAP="de-latin1-nodeadkeys.uni"
>
> which does not exist.

Fedora's console_init calls "loadkeys" with "-u", if its LANG has .UTF-8

  parent reply	other threads:[~2010-08-12 11:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-11 17:47 [PATCH] Fix autodetection of UNICODE keymap Andrey Borzenkov
2010-08-12 11:05 ` Harald Hoyer
     [not found]   ` <4C63D565.3030405-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2010-08-12 11:08     ` Harald Hoyer [this message]
     [not found]       ` <4C63D629.4040204-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2010-08-12 11:48         ` Re[2]: " Andrey Borzenkov
     [not found]           ` <E1OjWGr-0004HZ-00.arvidjaar-mail-ru-KwwT3n/ykh4edp2WBT/QOw@public.gmane.org>
2010-08-12 12:28             ` Harald Hoyer
     [not found]               ` <4C63E8EC.7040507-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2010-08-12 17:26                 ` Andrey Borzenkov
2010-08-12 11:52 ` Amadeusz Żołnowski

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=4C63D629.4040204@redhat.com \
    --to=harald-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
    --cc=aidecoe-2qtfh70TtYba5EbDDlwbIw@public.gmane.org \
    --cc=arvidjaar-JGs/UdohzUI@public.gmane.org \
    --cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    /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. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox