From: Michal Jaegermann <michal@harddata.com>
To: John Levon <levon@movementarian.org>,
linux-kernel@vger.kernel.org, Mikael Pettersson <mikpe@csd.uu.se>
Subject: Re: [2.5] initrd/mkinitrd still not working
Date: Mon, 20 Jan 2003 19:18:38 -0700 [thread overview]
Message-ID: <20030120191838.A7174@mail.harddata.com> (raw)
In-Reply-To: <20030120193546.GC1314@mars.ravnborg.org>; from sam@ravnborg.org on Mon, Jan 20, 2003 at 08:35:46PM +0100
On Mon, Jan 20, 2003 at 08:35:46PM +0100, Sam Ravnborg wrote:
> On Mon, Jan 20, 2003 at 07:19:21PM +0000, John Levon wrote:
> > Ooops, I was mis-remembering commit logs. I meant :
> >
> > http://linus.bkbits.net:8080/linux-2.5/user=kai/cset@1.838.1.86?nav=!-|index.html|stats|!+|index.html|ChangeSet
>
> OK, this is something else.
> Making the shift to the extension .ko allowed the syntax:
> make fs/ext2/ext2.ko or whatever module we want to build.
>
> Thats very nice when developing on a module to speed up things.
Well, yes, but while installing into a final location all these .ko
files could be renamed to have .o extensions. This would avoid
screwing up user-space utilities. It is not that difficult to
fix mkinitrd to try _both_ ways (I do not know how many folks runs
exclusively 2.5 kernels) but who knows how many other things
will have to be modified introducing gratituos incompatibilities.
Michal
next prev parent reply other threads:[~2003-01-21 2:09 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 [this message]
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
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=20030120191838.A7174@mail.harddata.com \
--to=michal@harddata.com \
--cc=levon@movementarian.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