From: Geoffrey Gallaway <geoffeg@sin.sloth.org>
To: linux-kernel@vger.kernel.org
Subject: Error in documentation?
Date: Mon, 18 Jun 2001 11:15:11 -0400 [thread overview]
Message-ID: <20010618111510.A27662@sin.sloth.org> (raw)
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?
Geoffeg
--
Geoffrey Gallaway ||
geoffeg@sloth.org || Clones are people two.
D e v o r z h u n ||
next reply other threads:[~2001-06-18 15:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-18 15:15 Geoffrey Gallaway [this message]
2001-06-18 16:04 ` Error in documentation? Steven Walter
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=20010618111510.A27662@sin.sloth.org \
--to=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;
as well as URLs for NNTP newsgroup(s).