From: John Weber <weber@nyc.rr.com>
To: linux-kernel@vger.kernel.org
Subject: Re: How to compile on one machine and install on another?
Date: Tue, 19 Jun 2001 22:23:47 -0400 [thread overview]
Message-ID: <3B300933.2090807@nyc.rr.com> (raw)
In-Reply-To: <fa.o4pbsqv.26md2n@ifi.uio.no> <fa.go24tnv.1v60h9a@ifi.uio.no>
Alan Cox wrote:
>>I am trying to compile the 2.2.19 kernel one one machine for installation
>>on another. I believe I need to do more than just copy over bzImage and
>>modify lilo.conf, but I don't know what. Is there documentation somewhere
>>on how to do this? Thanks.
>>
>
> 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
On a related note... is System.map also necessary? Anyone care to explain
what System.map does? I have noticed that my kernel works with or
without that file, but just figured it was a good question to ask in
this thread.
next parent reply other threads:[~2001-06-20 2:28 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.o4pbsqv.26md2n@ifi.uio.no>
[not found] ` <fa.go24tnv.1v60h9a@ifi.uio.no>
2001-06-20 2:23 ` John Weber [this message]
2001-06-20 2:50 ` How to compile on one machine and install on another? Mike Castle
2001-06-20 2:58 ` Keith Owens
2001-06-19 21:04 McHarry, John
-- 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=3B300933.2090807@nyc.rr.com \
--to=weber@nyc.rr.com \
--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).