public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Gabriel Rocha <grocha@onesecure.com>
To: "McHarry, John" <john.mcharry@gemplex.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: How to compile on one machine and install on another?
Date: Tue, 19 Jun 2001 14:32:53 -0700	[thread overview]
Message-ID: <20010619143253.F81548@onesecure.com> (raw)
In-Reply-To: <A5F553757C933442ADE9B31AF50A273B028DB4@corp-p1.gemplex.com>
In-Reply-To: <A5F553757C933442ADE9B31AF50A273B028DB4@corp-p1.gemplex.com>; from john.mcharry@gemplex.com on Tue, Jun 19, 2001 at 04:32:03PM -0400

[-- Attachment #1: Type: text/plain, Size: 1478 bytes --]

you could always compile on one machine and nfs mount the /usr/src/linux
and do a make modules_install from the nfs mounted directory...

,----[ On Tue, Jun 19, at 04:32PM, McHarry, John 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.
| -
| To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
| the body of a message to majordomo@vger.kernel.org
| More majordomo info at  http://vger.kernel.org/majordomo-info.html
| Please read the FAQ at  http://www.tux.org/lkml/
`----[ End Quote ]---------------------------

-- 
Gabriel Rocha (grocha@onesecure.com) - 1-877-4-1SECURE
OneSecure, Inc. Sunnyvale Security Operations Center (GMT -0700)

-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: 2.6.3ia

mQCNAzrYQA8AAAEEAL/fjYD12U8QNO0PJX30zYd+0Wg1aZq+jPp34hTiMXrGg2bv
VE2hwrcz4iILCaQ5KlncteycMx6VL7u0tnIkxnT0M8fAPuS4VpqB/tS/mr3RcHLa
52+TRZ45KnZt/6pp+pc9zJM8STJvGatfF+YPYKtzEM3mFL4OEnMJdtsEFkx1AAUT
tCRHYWJyaWVsIFJvY2hhIDxncm9jaGFAb25lc2VjdXJlLmNvbT6JAJUDBRA62EAP
cwl22wQWTHUBATrVA/9Z+/pUsd0nV6ZtOn014Q9hJ1TUzhzVcNVF1zUufTHTwLO1
gnKaomNj1Fb+pwGK3ZxNqomUTAnCXCU3HxQ0DkG8OIjzuOIr08Lv57pA9u/yjlTR
IOV5REUNFWD0ogKLAlVG9wp3IsSgntjToB/rj75siVrBapqzbgR+Dcs3nb8Ijg==
=HwqX
-----END PGP PUBLIC KEY BLOCK-----

[-- Attachment #2: Type: application/pgp-signature, Size: 290 bytes --]

  parent reply	other threads:[~2001-06-19 21:32 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-19 20:32 How to compile on one machine and install on another? 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 [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2001-06-19 21:04 McHarry, John
     [not found] <fa.o4pbsqv.26md2n@ifi.uio.no>
     [not found] ` <fa.go24tnv.1v60h9a@ifi.uio.no>
2001-06-20  2:23   ` John Weber
2001-06-20  2:50     ` Mike Castle
2001-06-20  2:58     ` 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=20010619143253.F81548@onesecure.com \
    --to=grocha@onesecure.com \
    --cc=john.mcharry@gemplex.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