Kernel Compilation
Steve Holmes
steve at holmesgrown.com
Sun Jan 9 11:25:21 EST 2005
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I would like to add some additional comments about kernel
recompilation if possible. I am currently using a 2.6.9 kernel on my
Slackware 10.0 settup here.
When untarring the kernel source from ftp.kernel.org, let it go ahead
and dump into linux-2.6.10 (or whatever version) into /usr/src. in
Slackware /usr/src/linux is symbolicly linked to the current version
anyway. The current configuration generated by a 'make menuconfig' is
.config built at the top of the linux source tree. As suggested
earlier, I would copy this .config file into a safe place like your
personal home directory so it can be brought back in the next time you
do a kernel compile. From what I've read in the README in linux-2.6
kernels, you only have to type 'make' to build kernel static source
and modules. I just then do a separate 'make modules_install' when
I'm ready to install the modules for prime time use. I also have a
couple simple shell scripts that copy the compiled kernel from the
../../../boot directory of the kernel source tree over to the /boot
directory. I also use lilo to maintain a separate boot label with
this kernel image and preserve one older one incase I break it.
Hope this helps.
- --
HolmesGrown Solutions
The best solutions for the best price!
http://ld.net/?holmesgrown
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFB4VrwWSjv55S0LfERAmIhAJ4r6TLDKPAwcs2o/yc3lU+dyEbFRwCePf6t
f7kVrPBs1UriBqv3BrQ40Ng=
=+UQV
-----END PGP SIGNATURE-----
More information about the Speakup
mailing list