All of lore.kernel.org
 help / color / mirror / Atom feed
From: Harald Hoyer <harald-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: "Amadeusz Żołnowski" <aidecoe-2qtfh70TtYba5EbDDlwbIw@public.gmane.org>
Cc: initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [RFC] console_init.c in i18n module
Date: Mon, 14 Jun 2010 08:46:01 +0200	[thread overview]
Message-ID: <4C15D029.6040906@redhat.com> (raw)
In-Reply-To: <20100614083102.16f35a59-YdJE6FOikKfe60hTmSeVGxfX6IwIUJvj@public.gmane.org>

On 06/14/2010 08:31 AM, Amadeusz Żołnowski wrote:
> Hello everyone,
>
> I'm trying to find a way to make i18n distro independent or at least
> more flexible.
>
> Module 10redhat-i18n depends on two programs from RH initscripts
> package: console_init and console_check.  Those tools are called by udev
> and if we deliver just keymaps and few things like loadkey we're fine.
> But… console_* are RH specific stuff (included in initscript package).
> I see two easy approaches:
>
>      * Putting its sources into Dracut tree beside switch_root.c.
>        They don't depend on any library, so it should be easy.
>      * Rewrite as a shell script (but it's redundant work if the first
>        way is OK).
>
> Moreover console_check isn't installed by Dracut at all, but it's in
> default “10-console.rules” rule.  This tool just setup speed for serial
> console which we do by kernel params, so I guess we can skip it.  In
> that case modified 10-console.rules should be delivered inside i18n
> module.
>
> What do you think about it?
>
>
> Cheers,
> Amadeusz Żołnowski
>

I would be happy, if we had a shell replacement, or a small rewrite without the 
libglib (huge lib only referenced by console_init).

      parent reply	other threads:[~2010-06-14  6:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-14  6:31 [RFC] console_init.c in i18n module Amadeusz Żołnowski
     [not found] ` <20100614083102.16f35a59-YdJE6FOikKfe60hTmSeVGxfX6IwIUJvj@public.gmane.org>
2010-06-14  6:46   ` Harald Hoyer [this message]

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=4C15D029.6040906@redhat.com \
    --to=harald-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
    --cc=aidecoe-2qtfh70TtYba5EbDDlwbIw@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.