Linux Hotplug development
 help / color / mirror / Atom feed
From: Erik van Konijnenburg <ekonijn@xs4all.nl>
To: linux-hotplug-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: [ANNOUNCE] yaird 0.0.11, a mkinitrd based on hotplug concepts
Date: Tue, 09 Aug 2005 21:25:20 +0000	[thread overview]
Message-ID: <20050809232520.B12865@banaan.localdomain> (raw)

Version 0.0.11 of yaird is now available at:
	http://www.xs4all.nl/~ekonijn/yaird/yaird-0.0.11.tar.gz

Yaird is a proof of concept perl rewrite of mkinitrd.  It aims to
reliably identify the necessary modules by using the same algorithms
as hotplug, and comes with a template system to to tune the tool for
different distributions and experiment with different image layouts.
It requires a 2.6 kernel with hotplug.  There is a paper discussing it at:

	http://www.xs4all.nl/~ekonijn/yaird/yaird.html

Summary of user visible changes:
     * Support configuration file that determines what the generated
       image should do.  It replaces command line options for root
       file system selection and for NFS support.
     * The file /etc/hotplug/blacklist does not have to exist:
       this can be a machine without hotplug, or with a future
       hotplug version, where blacklisting is delegated to module-init-tools.
       Based on patch by Marian Andre <Marian.Andre@sq.sk>
     * Bugfix: expect characters A-Z, in kernel config entries.
     * Handle kernels that do not have ide-generic.

Changes in version 0.0.10 and 0.0.9 were too small to
merit an announcement:
     * Support legacy keyboard compiled as module.
     * Place the docs under GPL instead of GFDL for the benefit of Debian.

Regards,
Erik



-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

                 reply	other threads:[~2005-08-09 21:25 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=20050809232520.B12865@banaan.localdomain \
    --to=ekonijn@xs4all.nl \
    --cc=linux-hotplug-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.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