From: Rusty Russell <rusty@rustcorp.com.au>
To: Bill Davidsen <davidsen@tmr.com>
Cc: Mikael Pettersson <mikpe@csd.uu.se>,
linux-kernel@vger.kernel.org, Herbert Xu <herbert@debian.org>
Subject: Re: [2.5] initrd/mkinitrd still not working
Date: Wed, 29 Jan 2003 11:48:17 +1100 [thread overview]
Message-ID: <20030129005134.6E7E82C41B@lists.samba.org> (raw)
In-Reply-To: Your message of "Tue, 28 Jan 2003 12:10:49 CDT." <Pine.LNX.3.96.1030128120708.32466C-100000@gatekeeper.tmr.com>
In message <Pine.LNX.3.96.1030128120708.32466C-100000@gatekeeper.tmr.com> you w
rite:
> beating around the bush: how about adding mkinitrd to the other module
> stuff before 0.9.9 is really released, using the same .old technique used
> for insmod et al? It would allow people doing testing of both 2.4 and 2.5
> kernels to stop fighting build issues.
Hmm, unlike modutils, I've never even used mkinitrd, let alone read
the code (mmm... shell... yum!). For that reason alone I'm not the
guy to take it over (plus, I'm extremely lazy).
Herbert, I'd be happy to discuss any mkinitrd changes, or put a patch
into module-init-tools (or the FAQ?).
Thanks!
Rusty.
--
Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
next prev parent reply other threads:[~2003-01-29 0:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-20 14:57 [2.5] initrd/mkinitrd still not working Mikael Pettersson
2003-01-20 15:52 ` John Levon
2003-01-20 19:12 ` Sam Ravnborg
2003-01-20 19:19 ` John Levon
2003-01-20 19:35 ` Sam Ravnborg
2003-01-21 2:18 ` Michal Jaegermann
2003-01-21 17:02 ` Bill Davidsen
2003-01-28 1:03 ` Rusty Russell
2003-01-28 17:10 ` Bill Davidsen
2003-01-29 0:48 ` Rusty Russell [this message]
2003-01-29 1:56 ` Herbert Xu
2003-01-29 6:21 ` Rusty Russell
2003-02-02 15:28 ` Bill Davidsen
2003-02-03 0:59 ` Rusty Russell
-- strict thread matches above, loose matches on Subject: below --
2003-01-18 19:46 Bill Davidsen
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=20030129005134.6E7E82C41B@lists.samba.org \
--to=rusty@rustcorp.com.au \
--cc=davidsen@tmr.com \
--cc=herbert@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@csd.uu.se \
/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