All of lore.kernel.org
 help / color / mirror / Atom feed
From: Miles Lott <milos@insync.net>
To: chad@sgi.com
Cc: linux <linux@cthulhu.engr.sgi.com>
Subject: Re: Build a new kernel?
Date: Wed, 03 Mar 1999 04:21:04 +0000	[thread overview]
Message-ID: <36DCB8B0.9BA28845@insync.net> (raw)
In-Reply-To: 36DC3354.42E4BAE5@dallas.sgi.com

I can only speak to Intel, as I have yet to get Hardhat
booted.  Generally, I start with the kernel source rather than
an rpm.  Of course, upon install of a new dist, you start with
the dist's packaged version.  But I would replace that asap,
tailoring it based upon what you need.

RedHat separates the kernel into at least two rpms, though
kernel-headers.rpm is most likely a subset of the kernel-src.rpm,
consisting of only include files used for compiling other sources.

Get the 'real' kernel source.  Unpack it in /usr/src as linux/.
cd /usr/include; rm asm linux; ln -s /usr/src/linux/include/linux;
ln -s /usr/src/linux/include/asm; cd /usr/src/linux; read ;)

Menuconfig has quite a bit of online help, plus the Documentation
tree will help you become familiar with the available options.
make xconfig is nice as well, especially for browsing and immediate
recognition of dependencies that some choices enforce.  Other than
that, the Linux Kernel HOWTO, which I guess you have read.

Note that the completed configuration ends up in .config in the
top level of the source tree after make config, make menuconfig,
or make xconfig.  I like to keep a copy of this outside the
tree so that I can maintain some consistency from kernel to
kernel, rather than start over with each new src tree.

After running make (menu/x/)config, always do make dep;make clean;
I then do make zImage;make modules;make modules_install

Enjoy!

Chad Carlin wrote:
> 
> Could someone point me to some documentation on the proceedure
> for building a new linux kernel?
> 
> I need info like; prerequisite rpms, Guidance on what options to
> choose in menuconfig,  How to implement the new kernel, Do I
> need to modify any config files.
> 
> The documentation that I have found for intel-linux has so far
> has been similar but not quite the same. I haven't really looked
> for the "how to build a kernel for MIPS" docs yet.
> 
> I tried to build one on my intel-linux box for practice. It
> didn't go well.
> 
> Chad
> 
> --
>            -----------------------------------------------------
>             Chad Carlin                          Special Systems
>             Silicon Graphics Inc.                   972.205.5911
>             Pager 888.754.1597          VMail 800.414.7994 X5344
>             chad@sgi.com             http://reality.sgi.com/chad
>            -----------------------------------------------------
>         "flying through hyper space ain't like dusting crops, boy"

      reply	other threads:[~1999-03-03  4:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-03-02 18:52 Build a new kernel? Chad Carlin
1999-03-03  4:21 ` Miles Lott [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=36DCB8B0.9BA28845@insync.net \
    --to=milos@insync.net \
    --cc=chad@sgi.com \
    --cc=linux@cthulhu.engr.sgi.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 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.