From: Kevin Breit <mrproper@ximian.com>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: make install problems
Date: Tue, 30 Sep 2003 12:18:10 -0400 [thread overview]
Message-ID: <1064938690.1575.7.camel@localhost.localdomain> (raw)
In-Reply-To: <20030930083415.06f155ba.rddunlap@osdl.org>
On Tue, 2003-09-30 at 11:34, Randy.Dunlap wrote:
> On Tue, 30 Sep 2003 11:29:42 -0400 Kevin Breit <mrproper@ximian.com> wrote:
>
> | On Tue, 2003-09-30 at 11:14, Randy.Dunlap wrote:
> | > On Tue, 30 Sep 2003 09:16:19 -0400 Kevin Breit <mrproper@ximian.com> wrote:
> | >
> | > | Hey,
> | > | I setup a test6 kernel without module support. I did a make install
> | > | and got:
> | > |
> | > | Kernel: arch/i386/boot/bzImage is ready
> | > | sh /usr/src/linux-2.6.0-test6/arch/i386/boot/install.sh 2.6.0-test6
> | > | arch/i386/boot/bzImage System.map ""
> | > | /lib/modules/2.6.0-test6 is not a directory.
> | > | mkinitrd failed
> | > |
> | > | How can I fix this?
> | >
> | > We've seen this before, and I thought that we had determined that
> | > it was a tools problem. Is "depmod" in $PATH the depmod from
> | > modutils or the one from module-init-tools?
> | > I.e., what does 'depmod -V' say?
> |
> | modutils-2.4.22-8
> |
> | [root@kbreit linux-2.6.0-test6]# depmod -V
> | depmod version 2.4.22
> |
> |
> | > and what execs mkinitrd? I don't find it with a quick grep.
> |
> | No clue
>
> You need to use module-init-tools with 2.6.x, not modutils.
> You can find them at
> http://www.kernel.org/pub/linux/kernel/people/rusty/modules/
> Just get the latest version.
Why do I need this for a moduleless kernel?
Kevin
next prev parent reply other threads:[~2003-09-30 16:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-30 13:16 make install problems Kevin Breit
2003-09-30 15:14 ` Randy.Dunlap
2003-09-30 15:29 ` Kevin Breit
2003-09-30 15:34 ` Randy.Dunlap
2003-09-30 16:18 ` Kevin Breit [this message]
2003-09-30 16:25 ` Randy.Dunlap
2003-10-01 8:26 ` [patch] " Rob Landley
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=1064938690.1575.7.camel@localhost.localdomain \
--to=mrproper@ximian.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.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;
as well as URLs for NNTP newsgroup(s).