The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Matt Simonsen <matt_lists@careercast.com>
To: linux-kernel@vger.kernel.org
Subject: build kernel for server farm
Date: 06 Nov 2002 14:00:08 -0800	[thread overview]
Message-ID: <1036620009.1332.12.camel@mattsworkstation> (raw)

I am pretty familiar with the build process and kernel install for a
single Linux box, but I wanted to confirm I'm doing things in a sane way
for a large deployment. All the machines are the same hardware and
running standard setups.

First, I plan on compiling the kernel on a development box. From there
my plan is basically tar /usr/src/linux, copy to each box, untar, copy
bzImage and System.map to /boot, run make modules_install, edit
lilo.conf, run lilo.

Tips? Comments?

Thanks 
Matt


             reply	other threads:[~2002-11-06 21:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-06 22:00 Matt Simonsen [this message]
2002-11-06 23:13 ` build kernel for server farm Zwane Mwaikambo
2002-11-06 23:55   ` Matt Simonsen
2002-11-07  2:31 ` dee jay
2002-11-07  4:42 ` James Bourne
2002-11-07  9:23 ` Henning P. Schmiedehausen
2002-11-07 15:27 ` Denis Vlasenko

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=1036620009.1332.12.camel@mattsworkstation \
    --to=matt_lists@careercast.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