From: Jeff Garzik <jgarzik@pobox.com>
To: Erik van Konijnenburg <ekonijn@xs4all.nl>
Cc: linux-hotplug-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, "H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [ANNOUNCE] yaird, a mkinitrd based on hotplug concepts
Date: Thu, 17 Feb 2005 16:50:05 -0500 [thread overview]
Message-ID: <4215118D.3020902@pobox.com> (raw)
In-Reply-To: <20050217210620.A20645@banaan.localdomain>
Erik van Konijnenburg wrote:
> Features:
> - handles both initrd and initramfs.
Comments:
* Having a mkinitrd that's not a shell script is a godsend. I would
endorse yaird on that fact alone :)
* I've long wanted a "mkinitfoo" that would create .cpio.gz for
initramfs by default. So, good job there, too.
* Eventually your script will need pull in, into the initramfs, klibc
and programs linked against klibc.
Jeff
next prev parent reply other threads:[~2005-02-17 21:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-17 20:06 [ANNOUNCE] yaird, a mkinitrd based on hotplug concepts Erik van Konijnenburg
2005-02-17 21:50 ` Jeff Garzik [this message]
2005-02-19 17:28 ` Andreas Jellinghaus
2005-02-21 19:13 ` Erik van Konijnenburg
2005-03-17 8:26 ` Werner Almesberger
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=4215118D.3020902@pobox.com \
--to=jgarzik@pobox.com \
--cc=ekonijn@xs4all.nl \
--cc=hpa@zytor.com \
--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