Hopefully I'm not beating a dead horse too much here.  

Here's what I do to build a kernel on a debian box.

apt-get install kernel-source-2.x.x libncurses5-dev kernel-package
(if you want to use make xconfig -- nice for first time configs -- you need
to install some tk/tcl 8.2, etc.)
Answer a couple questions for kernel-package
cd /usr/src; bzcat kernel-source-2.x.x.tar.bz2 | tar xvf -; ln -s
kernel-source-2.x.x linux
(if I have an old config I cp it in there, or scp it usually from another
box)
cd /usr/src/linux; make-kpkg (I don't know if I like this method, though it
is very automated and simple.)
-- or --
cd /usr/src/linux; make menuconfig
{make clean; make dep; make bzlilo; make modules; make modules_install
-- or --
cd /usr/src/linux; make xconfig
make clean; make dep; make bzlilo; make modules; make modules_install

I've never had any problems... I do remember trying to figure the same
process out on redhat boxes, what a pain in the *ss.  You'd have to pay me
double to use redhat these days.

Blake Barnett
Sr. Unix Administrator
DevelopOnline

-----Original Message-----
From: Craig White [mailto:craigwhite@azapple.com]
Sent: Sunday, May 27, 2001 10:44 AM
To: plug-discuss@lists.PLUG.phoenix.az.us
Subject: RE: More Kernel 2.4 Q's


At the risk of boring everyone, I have ascertained this much information
regarding compiling a kernel on RedHat 7.1 though I am certain that the
process is likely to be much the same with most all other distributions...

The proper procedure to maintain the original kernel and ability to boot
from that kernel & set of modules when compiling a new kernel would be to:

first - install
   kernel-source-2.4.2-2.i386.rpm (located on Binary CD 2)

cd /usr/src/linux-2.4.2/configs
   cp (desired config file) .config
   (i.e. cp kernel-2.4.2-i586.config .config

cd .. (your path should be /usr/src/linux-2.4.2 or whichever source you
intend to compile)

make mrproper
 (only necessary if previous attempts at compiling have failed)
 (not necessary if fresh untar/rpm sources)
make EXTRAVERSION=-foo menuconfig
make EXTRAVERSION=-foo dep
make EXTRAVERSION=-foo clean
 (only necessary if previous attempts at compiling have failed)
 (not necessary if fresh untar/rpm sources)
make EXTRAVERSION=-foo bzImage
make EXTRAVERSION=-foo modules
make EXTRAVERSION=-foo modules_install

---
note to Steve - initial configuration of make menuconfig (or gui's
equivalent) would be obtained from the file called .config in the configs
folder in the /usr/src/linux-version tree.

Hey as of last Wednesday I had never compiled a new kernel and in fact was
intimidated by the process. I would probably recommend that the first time
or two, you don't do it on a production computer in case you screw up and
forget to protect the initially installed kernel & modules from being
over-written.

Craig

----:----|----:----|----:----|----:----|----:----|----:----|
- Craig White - PO Box 8634 - Scottsdale, Arizona - 85252
- e-mail address ................ - CraigWhite@AzApple.com
- world wide web address ........ - http://www.AzApple.com
- e-mail my pager address ....... - 6023779752@airtouch.net
- cellular phone ................ - (602) 377-9752
- voice/facsimile ............... - (480) 945-8445
----:----|----:----|----:----|----:----|----:----|----:----|

________________________________________________
See http://PLUG.phoenix.az.us/navigator-mail.shtml if your mail doesn't post
to the list quickly and you use Netscape to write mail.

PLUG-discuss mailing list  -  PLUG-discuss@lists.PLUG.phoenix.az.us
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss