public inbox for gentoo-soc@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Amadeusz Żołnowski" <aidecoe@aidecoe.name>
To: gentoo-soc <gentoo-soc@lists.gentoo.org>
Subject: [gentoo-soc] Dracut port - weekly progress - week 4
Date: Mon, 21 Jun 2010 23:54:51 +0200	[thread overview]
Message-ID: <20100621235451.0e629ce2@etiriah.ds.pg.gda.pl> (raw)

[-- Attachment #1: Type: text/plain, Size: 1326 bytes --]

Hello everyone,


Exam period still lasts, but it's starting to be better.

Last week I spend on writing new generic i18n module for Dracut. The
ready install script is posted to mailing list (at vger.kernel.org).
Here's a quote of abstract of this message:

    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.

After i18n will be fully finished (soon :-)), I'll focus on network
stuff.

References:

    * Initramfs mailing list:
      http://www.spinics.net/lists/linux-initramfs/
    * My Dracut fork repo: http://github.com/aidecoe/dracut
    * My blog: http://blog.aidecoe.name/


Cheers,
Amadeusz Żołnowski

-- 
PGP key: 1024D/C284750D

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

                 reply	other threads:[~2010-06-21 21:55 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20100621235451.0e629ce2@etiriah.ds.pg.gda.pl \
    --to=aidecoe@aidecoe.name \
    --cc=gentoo-soc@lists.gentoo.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