Re: How to compile on one machine and install on another?

Gabriel Rocha
2001-06-20T00:42:22Z

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

the 'compile in one place and export the product via nfs' mentality
really kicks in under *bsd, where you may have a server farm and want to
upgrade all at once...the tarball idea works for one machine, but for
multiples, its all about exporting it... just my 2 cents. --gabe

,----[ On Tue, Jun 19, at 07:24PM, Kelledin Tane wrote: ]--------------
| Gabriel Rocha wrote:
|
| > 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...
|
| The way I've always managed this sort of thing is to tar up your kernel source,
| transfer it to the "compile box" however you please, then do all the compile
| steps except the "make modules_install" and the copying of the kernel image.
| Then tar up the compiled source tree, transfer it over to the box you want to
| install on, untar it, and do the rest of the steps (the "make modules_install"
| and the copying of the kernel image). Just make sure that all the systems
| involved have about the same system time, else you'll get the message, "Clock
| skew detected. Your build may be incomplete."
|
| One day I managed to get egcs-2.91.66 to compile against glibc-2.2, and I never
| had to do that stuff again. ;)
|
| Kelledin
|
| bash-2.05 $ kill -9 1
| init: Just what do you think you're doing, Dave?
|
| -
| 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 --]