public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: J Sloan <jjs@toyota.com>
To: Peter Moscatt <pmoscatt@yahoo.com>
Cc: Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: Kernel Recommended Defaults
Date: Tue, 25 Sep 2001 15:36:48 -0700	[thread overview]
Message-ID: <3BB10700.F1B89F5@lexus.com> (raw)
In-Reply-To: <20010925215741.47198.qmail@web14704.mail.yahoo.com>

Peter Moscatt wrote:

> I am about to compile and install my first kernel and
> want to make sure I have things pretty well set before
> I create the image.
>
> Is there guides available where they show recommended
> defaults - especially in the Network arena ?

1. although the initrd is a nice hack, I generally
avoid all that and compile all the requirements of
the root file system into the kernel -

2. everything else, I generally compile as modular.
this is extremely helpful in troubleshooting, e.g.
you can load/unload drivers without a reboot.

3. It doesn't hurt to have modules compiled for
cards you don't need, since they will not be
loaded. However, you want to avoid the opposite
scenario - not having the driver you need.

4. the defaults are usually sane, but look at
each and every one the first time you do a
kernel config.

5. DO NOT simply blow away your old kernel -
you will be sorry if you do. leave the old kernel
intact as a fallback, and make the necessary
edits to lilo, grub or whatever boot manager
you are using.

Regards,

jjs




      parent reply	other threads:[~2001-09-25 22:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-25 21:57 Kernel Recommended Defaults Peter Moscatt
2001-09-25 22:13 ` Ian Schroeder-Anderson
2001-09-25 22:36 ` J Sloan [this message]

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=3BB10700.F1B89F5@lexus.com \
    --to=jjs@toyota.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pmoscatt@yahoo.com \
    /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