From: Steven Walter <srwalter@yahoo.com>
To: Geoffrey Gallaway <geoffeg@sin.sloth.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Error in documentation?
Date: Mon, 18 Jun 2001 11:04:57 -0500 [thread overview]
Message-ID: <20010618110457.A21328@hapablap.dyn.dhs.org> (raw)
In-Reply-To: <20010618111510.A27662@sin.sloth.org>
In-Reply-To: <20010618111510.A27662@sin.sloth.org>; from geoffeg@sin.sloth.org on Mon, Jun 18, 2001 at 11:15:11AM -0400
It does appear that the documentation regarding this is out of date.
However, you can still install modules to a given location by:
INSTALL_MOD_PATH="/path/to/modules" make modules_install
Had to dig through the Makefile for that, though it may actually be
documented somewhere.
On Mon, Jun 18, 2001 at 11:15:11AM -0400, Geoffrey Gallaway wrote:
> linux/Documentation/modules.txt says that I should find my modules in
> "linux/modules" after running "make modules". However, this is
> apparently not true as I see no modules directory.
>
> I am trying to compile a kernel with lots of modules for a machine
> without a network connection. To move the kernel, I simply copy it to
> floppy and move it over to the other machine. However, for the modules,
> is my only choice appears to be "make modules-install" then tar up
> /lib/modules/kernel-release/ and then remove the directory. Is there a
> cleaner way to handle this?
--
-Steven
In a time of universal deceit, telling the truth is a revolutionary act.
-- George Orwell
prev parent reply other threads:[~2001-06-18 16:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-18 15:15 Error in documentation? Geoffrey Gallaway
2001-06-18 16:04 ` Steven Walter [this message]
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=20010618110457.A21328@hapablap.dyn.dhs.org \
--to=srwalter@yahoo.com \
--cc=geoffeg@sin.sloth.org \
--cc=linux-kernel@vger.kernel.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