Noah L. Meyerhans wrote:
On Mon, Aug 04, 2003 at 03:29:51PM -0500, Marino Fernandez wrote:
I cannot help you with the debian way... that I found more complex than the
Download a pristine kernel (get 2.6.0-test2)
Untar kernel in /usr/src
mv linux linux~
ln -s linux-2.6.0-test2 linux
make menuconfig or make xconfig
Put bzimage in /boot, rename it vmlinuz-2.6.0-test2
Update lilo or grub
Please tell me how that is less complex than
$ cd <kernel source dir>
$ fakeroot make-kpkg --config menu kernel_image
$ sudo dpkg -i ../kernel-image-<whatever the version was>.deb
$ sudo reboot
I just don't get it.
Plus, the Debian way is much easier, IMHO, for compiling on one machine,
and installing on another. This is useful in cases where you:
1) Don't want to bog down a machine with compiling a kernel (I like to
compile during the day when I'm awake enough to be sure I caught
everything... people get mad at me if all the RAM disappears on my
spamassassin server, or if I steal all the CPU cycles on my MySQL server).
2) Don't want to put gcc et. al. on a machine (for security or space
3) Have more than one machine with the same hardware, etc. If only one
kernel config is required, why recompile 10 times (or compile once, copy
bzImage to all the machines, copy the modules ot all the machines,
reboot, discover you forgot system.map on one, and forgot to run LILO on
Very handy to compile on one machine, scp kernal_image.servername.1
servername:/usr/local/src and dpkg -i the image...
ETN Systems Inc.
2125 1st Ave East
Hibbing MN 55746