From: Rusty Russell <rusty@rustcorp.com.au>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: rob@landley.net, linux-kernel@vger.kernel.org
Subject: Re: Make modules_install doesn't create /lib/modules/$version
Date: Fri, 19 Sep 2003 12:25:56 +1000 [thread overview]
Message-ID: <20030919024455.834992C0F1@lists.samba.org> (raw)
In-Reply-To: Your message of "Thu, 18 Sep 2003 09:15:11 MST." <20030918091511.276309a6.rddunlap@osdl.org>
In message <20030918091511.276309a6.rddunlap@osdl.org> you write:
> On Thu, 18 Sep 2003 03:21:40 -0400 Rob Landley <rob@landley.net> wrote:
>
> | I've installed -test3, -test4, and now -test5, and each time make
> | modules_install died with the following error:
> |
> | Kernel: arch/i386/boot/bzImage is ready
> | sh arch/i386/boot/install.sh 2.6.0-test5 arch/i386/boot/bzImage System.map ""
> | /lib/modules/2.6.0-test5 is not a directory.
Looks like arch/i386/boot/install.sh is calling ~/bin/installkernel or
/sbin/installkernel, which is not creating the directory.
Should depmod create the directory? It can, of course, but AFAICT the
old one didn't.
Maybe a RedHat issue?
Rusty.
--
Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
next prev parent reply other threads:[~2003-09-19 2:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-18 7:21 Make modules_install doesn't create /lib/modules/$version Rob Landley
2003-09-18 16:15 ` Randy.Dunlap
2003-09-19 2:25 ` Rusty Russell [this message]
2003-09-19 5:41 ` Martin Schlemmer
2003-09-19 9:10 ` Mikael Pettersson
2003-09-19 16:01 ` Martin Schlemmer
2003-09-19 19:16 ` Rob Landley
2003-09-19 19:04 ` Rob Landley
2003-09-18 17:54 ` Sam Ravnborg
2003-09-19 8:41 ` Bas Mevissen
-- strict thread matches above, loose matches on Subject: below --
2003-09-19 21:39 Mikael Pettersson
2003-09-22 10:55 ` Rob Landley
2003-09-22 12:05 ` Mikael Pettersson
2003-09-22 13:02 ` Martin Schlemmer
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=20030919024455.834992C0F1@lists.samba.org \
--to=rusty@rustcorp.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.org \
--cc=rob@landley.net \
/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