From: "McHarry, John" <john.mcharry@gemplex.com>
To: "'Tom Diehl'" <tdiehl@pil.net>, linux-kernel@vger.kernel.org
Subject: RE: How to compile on one machine and install on another?
Date: Tue, 19 Jun 2001 17:04:02 -0400 [thread overview]
Message-ID: <A5F553757C933442ADE9B31AF50A273B028DB9@corp-p1.gemplex.com> (raw)
-----Original Message-----
From: Tom Diehl [mailto:tdiehl@pil.net]
Sent: Tuesday, June 19, 2001 4:55 PM
To: linux-kernel@vger.kernel.org
Subject: Re: How to compile on one machine and install on another?
On Tue, 19 Jun 2001, Alan Cox wrote:
> Other than making sure you configure it for the box it will eventually run
> on - nope you have it all sorted. If you use modules you'll want to
install
> the modules on the target machine too
What is the best way to install the modules? Is there a directory _all_ of
the modules exist in b4 you do "make modules_install". I usually end up
setting EXTRAVERSION to something unique and doing a make modules_install.
That way it does not hose up the modules for the build machine.
Is there a better way?
I found it puts the new ones in a unique directory under /lib/modules. I
just copied that also.
I didn't go into the issues, but I am getting an error message from the
target box that "/dev/md0 must be a nonpersistent RAID0 or LINEAR array!"
This is OK in 2.2.17, which is currently running on the machine.
next reply other threads:[~2001-06-19 21:03 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-19 21:04 McHarry, John [this message]
[not found] <fa.o4pbsqv.26md2n@ifi.uio.no>
[not found] ` <fa.go24tnv.1v60h9a@ifi.uio.no>
2001-06-20 2:23 ` How to compile on one machine and install on another? John Weber
2001-06-20 2:50 ` Mike Castle
2001-06-20 2:58 ` Keith Owens
-- strict thread matches above, loose matches on Subject: below --
2001-06-19 20:32 McHarry, John
2001-06-19 20:35 ` Alan Cox
2001-06-19 20:55 ` Tom Diehl
2001-06-19 21:04 ` Steven Walter
2001-06-19 21:11 ` Raphael Manfredi
2001-06-19 21:50 ` John R Lenton
2001-06-23 4:53 ` Anuradha Ratnaweera
2001-06-20 20:11 ` Maciek Nowacki
2001-06-21 3:10 ` Keith Owens
2001-06-19 21:32 ` Gabriel Rocha
2001-06-19 21:45 ` Eli Carter
2001-06-19 21:53 ` Gabriel Rocha
2001-06-19 22:42 ` Mike Castle
2001-06-20 0:24 ` Kelledin Tane
2001-06-20 0:42 ` Gabriel Rocha
2001-06-20 7:58 ` Helge Hafting
2001-06-21 2:42 ` Keith Owens
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=A5F553757C933442ADE9B31AF50A273B028DB9@corp-p1.gemplex.com \
--to=john.mcharry@gemplex.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tdiehl@pil.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;
as well as URLs for NNTP newsgroup(s).