All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Simonsen <matt_lists@careercast.com>
To: linux-kernel@vger.kernel.org
Subject: Re: build kernel for server farm
Date: 06 Nov 2002 15:55:02 -0800	[thread overview]
Message-ID: <1036626902.1331.30.camel@mattsworkstation> (raw)
In-Reply-To: <Pine.LNX.4.44.0211061813170.27141-100000@montezuma.mastecende.com>

On Wed, 2002-11-06 at 15:13, Zwane Mwaikambo wrote:
> On 6 Nov 2002, Matt Simonsen wrote:
> 
> > 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?
> 
> Network file system?

For /usr/src and the kernel distribution? Or for the whole boot process?

I use NFS already for several shared filesystems. NFS isn't quite
specific enough that I understand what you mean.

Could you give me a little more detail on exactly what you would use it
for? If I've overlooked a howto or obvious document please RTFM me- I'm
trying to learn from the pros here and would ideally like something that
will scale well to over 100 machines.

Matt



  reply	other threads:[~2002-11-06 23:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-06 22:00 build kernel for server farm Matt Simonsen
2002-11-06 23:13 ` Zwane Mwaikambo
2002-11-06 23:55   ` Matt Simonsen [this message]
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=1036626902.1331.30.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.