Recompiling kernel in Slackware, any special commands?
 

If I need to edit my .config file in my kernel, all I need to do is
Correct?
Make takes over 15 minutes to do, is there any way to speed it up?
Do I need to run mkinitrd each time I recompile my kernel?
Thank you for answering my questions.
~Romanus

you cant wait 15mins ? - only way to speed it up it to remove what you don't need

You will need to rerun lilo and mkinitrd. Personally I do not "make install", but manually copy the new image into /boot and edit lilo.conf. Don't blow away your working kernel until you've tested your new one. Notice that mkinitrd allows you change the name of the initrd.img so, again, you don't over-write your working configuration until you've tested your new one.

Brian

If you build in the drivers for stuff you need to boot the system into your custom kernel (e.g. file systems, drive controllers, etc) you can bypass the need for the initrd as well.

The best (or one of the best) kernel building guides for Slackware is available here, provided by Alien Bob: http://alien.slackbook.org/dokuwiki/...kernelbuilding

I prefer manually copying over the (very few) files needed instead of running `make install` just so I know exactly what I did and so it's basically impossible to screw anything up at all (the only possible system-wide screw-up is `make modules_install`, but as long as you're not compiling an identical kernel version as an already installed kernel, or if you changed the EXTRAVERSION option to prevent overwriting a directory in /lib/modules/, you should be fine). As a side note, if you build the kernel in your user's home directory (or even better a directory within your user's home directory...;)) then the ONLY commands needed to be run as root are `make modules_install` and when copying stuff over to /boot.

If you compile the filesystem used on your root partition (/) into the kernel, then you shouldn't need an initrd except in special cases. Otherwise, yes, you will need an initrd.

In those immortal words: Patience Grasshopper! :)

When I compiled my new kernel on my old 350 MHz PII, I needed 3-1/4 hours or so. With my new 2.3 GHz BE-2400 dual core AM2 and 2 GB of RAM (been 10 years since I bought a new box!) --- using the make -j4 option, I now compile the kernel in about 15 minutes. I'm like a pig in mud having to now "wait" a whopping 15 minutes. ;)

*) You don't need to rebuild your initrd.gz if the kernel version is the same.

*) If you don't do 'make clean' in the kernel source tree, the second build should be much faster if you just change a few things.

Took me 6 hours first time I did it. Fifteen minutes is just time for a coffee !

Although that approach may offer instant gratification (a quicker compile) I'd be wary of using it. Depending on what you changed in the kernel, it can be fine -- but if you don't know what you're doing it may do strange things. I always make sure to run `make mrproper` (or `make clean`) before compiling -- even immediately after untarring the sources (they're not always perfect when you download them).