All of lore.kernel.org
 help / color / mirror / Atom feed
From: Harald Hoyer <harald-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: haruo.tomita-g3qfMnKXm6lL9jVzuh4AOg@public.gmane.org
Cc: initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: (PATCH) force LANG=C for selinux load policy
Date: Tue, 31 May 2011 11:17:59 +0200	[thread overview]
Message-ID: <4DE4B247.6010005@redhat.com> (raw)
In-Reply-To: <4915AF3239D2024A92BCEC8BDAC566CE0116FA8A-9Dnl1bLEA2hgYsFYm0uEO7jjLBE8jN/0@public.gmane.org>

On 31.05.2011 10:19, haruo.tomita-g3qfMnKXm6lL9jVzuh4AOg@public.gmane.org wrote:
> Hi Harold,
> 
> Using Japanese ja_JP.UTF-8 environment, 
> the characters in load selinux policy message are garbled.
> This simple patch mainly adds force LANG=C to selinux load policy.
> 
> Kind regards,
> Haruo.
> 
> --- dracut-010/modules.d/98selinux/selinux-loadpolicy.sh.orig   2011-05-31 14:36:34.000000000 +0900
> +++ dracut-010/modules.d/98selinux/selinux-loadpolicy.sh        2011-05-31 14:38:44.000000000 +0900
> @@ -4,6 +4,11 @@
> 
>  # FIXME: load selinux policy.  this should really be done after we switchroot
> 
> +# We can't Japanese on normal console at boot time, so force LANG=C.
> +if [ "$LANG" = "ja_JP.UTF-8" ]; then
> +    LANG=C
> +fi
> +
>  rd_load_policy()
>  {
>      # If SELinux is disabled exit now

Hmm, why are the messages garbled? Is the console not set up correctly?

  parent reply	other threads:[~2011-05-31  9:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-31  8:19 (PATCH) force LANG=C for selinux load policy haruo.tomita-g3qfMnKXm6lL9jVzuh4AOg
     [not found] ` <4915AF3239D2024A92BCEC8BDAC566CE0116FA8A-9Dnl1bLEA2hgYsFYm0uEO7jjLBE8jN/0@public.gmane.org>
2011-05-31  9:17   ` Harald Hoyer [this message]
     [not found]     ` <4DE4B247.6010005-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2011-06-01  8:02       ` haruo.tomita-g3qfMnKXm6lL9jVzuh4AOg
     [not found] ` <1306833291-sup-8652@ittemni>
2011-06-01  8:02   ` haruo.tomita-g3qfMnKXm6lL9jVzuh4AOg

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=4DE4B247.6010005@redhat.com \
    --to=harald-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
    --cc=haruo.tomita-g3qfMnKXm6lL9jVzuh4AOg@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 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.