mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mikael Pettersson <mikpe@csd.uu.se>
To: rob@landley.net
Cc: azarah@gentoo.org, linux-kernel@vger.kernel.org,
	rddunlap@osdl.org, rusty@rustcorp.com.au
Subject: Re: Make modules_install doesn't create /lib/modules/$version
Date: Mon, 22 Sep 2003 14:05:22 +0200	[thread overview]
Message-ID: <16238.58754.128179.710670@gargle.gargle.HOWL> (raw)
In-Reply-To: <200309220655.43275.rob@landley.net>

Rob Landley writes:
 > > depmod does not create any directories, 'make modules_install' does.
 > 
 > Although make install dies on a red hat 9 system trying to look at the modules 
 > directory if modules_install isn't done first.  Maybe it's an RH 9 bug.  I 

RH9's /sbin/installkernel tries to run /sbin/new-kernel-pkg in order to
build a new initrd. This will almost certainly fail if your modules
directory isn't already populated at this point.

make modules_install; make install
in that order solves the problem.

If you don't like RH's installkernel then you can always write
your own and put it in ~/bin. That's what I did a long time ago
to make it lilo-friendly. (RH prefers that POS grub.)

 > install" now, yet make install doesn't install modules.  Is there a reason 
 > make install does NOT install modules for a modular kernel?

It hasn't before. I doubt very many people have a major problem with it.

  reply	other threads:[~2003-09-22 12:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-19 21:39 Mikael Pettersson
2003-09-22 10:55 ` Rob Landley
2003-09-22 12:05   ` Mikael Pettersson [this message]
2003-09-22 13:02   ` Martin Schlemmer
  -- strict thread matches above, loose matches on Subject: below --
2003-09-18  7:21 Rob Landley
2003-09-18 16:15 ` Randy.Dunlap
2003-09-19  2:25   ` Rusty Russell
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

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=16238.58754.128179.710670@gargle.gargle.HOWL \
    --to=mikpe@csd.uu.se \
    --cc=azarah@gentoo.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rddunlap@osdl.org \
    --cc=rob@landley.net \
    --cc=rusty@rustcorp.com.au \
    /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

all inboxes | Powered by JetHome®