mkinitrd unification across distributions
 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] Generic I18N module - install script
Date: Tue, 22 Jun 2010 11:22:32 +0200	[thread overview]
Message-ID: <4C2080D8.6040400@redhat.com> (raw)
In-Reply-To: <20100620185919.19b9c83a-YdJE6FOikKfe60hTmSeVGxfX6IwIUJvj@public.gmane.org>

On 06/20/2010 06:59 PM, Amadeusz Żołnowski wrote:
> Hello everyone,
>
> I'd like to present a draft of install script of new generic i18n
> module.
>
>
> ~ Abstract ~
>
> Different distros have variables holding keyboard settings, fonts and so
> in different files and even under different names.  Sometimes it's
> “SYSFONT” in /etc/sysconfig/i18n, sometimes it's “consolefont” in
> /etc/conf.d/consolefont.  I came up with idea to hold mappings in
> configuration file (dracut.conf or dracut.conf.d/«distro».conf). The
> script gathers variables and prepares two “unified” files inside
> Dracut overlay.
>
> The rest of the script is quite the same as redhat-i18n but some tweaks.
> Dracut uses console_init written in C included in initscripts RPM, but
> I'm gonna rewrite it in bash and then i18n module will be fully generic.
>
>
> Please post here any doubts, questions, suggestions, insults… ;-)


>
> # $@ = list in format specified below (BNF notation)
> #
> #<list>  ::=<element>  |<element>  " "<list>
> #<element>  ::=<conf-file-name>  ":"<map-list>
> #<map-list>  ::=<mapping>  |<mapping>  ","<map-list>
> #<mapping>  ::=<src-var>  "-"<dst-var>  |<src-var>
> #
> # We assume no whitespace are allowed between symbols.
> #<conf-file-name>  is a file holding<src-var>  in your system.
> #<src-var>  is a variable holding value of meaning the same as<dst-var>.
> #<dst-var>  is a variable which will be set up inside initramfs.
> # If<dst-var>  has the same name as<src-var>  we can omit<dst-var>.
> #
> # Hope it's clear. ;-)

Hmm, what about varnames with a "-" ? You might want to use "@".

  parent reply	other threads:[~2010-06-22  9:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-20 16:59 [RFC] Generic I18N module - install script Amadeusz Żołnowski
     [not found] ` <20100620185919.19b9c83a-YdJE6FOikKfe60hTmSeVGxfX6IwIUJvj@public.gmane.org>
2010-06-22  9:22   ` Harald Hoyer [this message]
     [not found]     ` <4C2080D8.6040400-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2010-06-22  9:42       ` Harald Hoyer

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=4C2080D8.6040400@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox