Guys, I did it many times, and now I have to work with MV embedded kernel distribution, trying to modify it slightly. The problem is that it takes ages (more than 30 minutes on a high end Solaris system) to complete make even if I just change one .c or .S file.

What's the deal - is this expected or am I missing something?

LOL! I have the advantage of only doing it for fun! I have used several 'nix os's at work like aix, solaris and os2 (is os2 nix-like?) even older stuff like rmx and forth but luckily not intensely enough to bore me (yet!!).

2damncommon: if you upgrade your kernel with a precompiled kernel with RPM or APT, it's still a distro kernel, although it takes "initial" out of "I always use the distro's initial kernel". The first option applies.

If you make your own home compiled kernel, the three other options apply.

*edit*:
Agasfer: if it's just a quick modification, a module or tiny feature for testing, consider not executing "make clean". That clears all the .o files when you do. If you skip "make clean" too often, however, you might end up with a broken kernel eventually. In that case, consider "make clean", or when you are releasing a final kernel for many box or devices.

Back in the 50's and early 60's the kids would get an old car, strip it down and beef up the engine, and tinker with it to get every ounce of speed they could, build what they called a "hot-rod". Now maybe they get an old computer, strip it down (format HD - HOORAY! FREEDOM!), drop a new engine in there (Linux), tinker and get another hot-rod. :-D

Looks like I'm "pregnant" again.

I compile countless times a week just to watch the process take place over Lara Crofts boobs in my transparent aterm.

And when customers are in my shop working with me, I like to pipe the compile output to an external Digtal DEC Terminal. It is cause for conversation which in turn makes them stay longer which in turn racks up the hours I bill them for.

Just kidding around though...

Great poll and thread!

In all honestly, I re-compile weekly.

Have a good one,
Scott

Ok don't laugh at me here but as a new comer to Linux I have a question, and please don't tell me that I am in the wrong thread.
As you guys talk about compiling kernels and all that, Can some one explaine what are Kernels and how do you compile them?

Being a new linux user, I installed my first kernel yesterday(2.6.16.8). It took about 10 compilations, but now it works. Except I can streamline some stuff still, so I think I'll hit 15 compilations before the day is over

The kernel is the computer core. It has the drivers to make the computer function properly. The keyboard, the mouse, the screen, the buttons, ACPI, audio, wireless, CD/DVD, Harddrive, DMA... blablabla...

A module is a removable piece of kernel code that can be inserted and removed at will from the kernel. Compilling modules is better than compilling directly into the kernel sometimes, making a smaller kernel, and giving you the option to load the piece of code only when nessessary, making a faster boot time. (see initng for cool boot time speed up)

Now, to compile a kernel:
if it's a 2.4 to 2.6 kernel migration, online howtos a better suited to that.
if it's a 2.6 to 2.6 kernel upgrade, you can use the old config as a guideline or base config.

extract the kernel into /usr/src and symlink the directory to /usr/src/linux using the command "mc" (midnight commander) or ln (man ln)

(change directory) cd /usr/src/linux
(optional) cp /path/to/config .config
(for new config) make defconfig

(to edit config)
(console) make menuconfig
OR
(GUI) make xconfig

(makes bzImage and modules) make
(install modules) make modules_install

(installs kernel image) cp arch/i386/boot/bzImage /boot/kernel-2.6.[version]
(installs map) cp System.map /boot/System.map-2.6.[version]

edit lilo or just boot up if grub or done with lilo.

(to clean kernel) make clean
(to really clean kernel and remove configs) make mrproper

The 2.6 menuconfig has a new look but I found out I left so many drivers and support modules in the old config (combination of thinking 'better to have and not need than need and not have' and 'enough already, I'm tired, let's see some action!') I spent about 3 hours total going through and stripping what I (think) I don't need. Lots of trust in my 'lshw' and 'lspci' listings.

Noticed that ALSA support was an option in the 2.6.8 config, not sure if it was there in 2.4.27. Anyway, it's compiling now <* fingers crossed *>.

I know how you feel. Everytime I compile I always get a nervous feeling like I hope I didn't forget something.

When compilling a kernel in a tty or term, I switch to another tty/term, cat and grep the .config file to make sure I didn't forget anything

If I do, I make clean, make menuconfig, and start make again

What is "tty"? I'm assumging term stands for terminal. I googled it, and this is what I found, but I don't really get what it means. Can anyone explain?

tty from O'Reilly

151 "tty" foldoc "The Free On-line Dictionary of Computing (27 SEP 03)"
tty

<hardware> /tit'ee/ ({ITS} pronunciation, but some {Unix}
people say it this way as well; this pronunciation is not
considered to have sexual undertones), /T T Y/

1. {teletypewriter}.

2. (Especially {Unix}) Any terminal at all; sometimes used to
refer to the particular terminal controlling a given job (it
is also the name of a Unix command which outputs the name of
the current controlling terminal).

3. ({Unix}) Any {serial port}, whether or not the device
connected to it is a terminal; so called because under Unix
such devices have names of the form tty*. Ambiguity between
senses 2 and 3 is common but seldom bothersome.

4. A {TDD}.

[{Jargon File}]

(1995-11-23)

CTRL+ALT+Fn where n is 1 < n < 6 is a tty and 7 is usually your X/Xorg session.

I will now betray my age by mentioning that the genesis of the term 'TTY' came from the
old Western Union TeleTYpe line printers, which were originally connected to mainframes via telecommunication lines at speeds from about 50-110bps and spit out hardcopy listings on green bar fanfold paper. *I'm getting choked up just thinking about it.*

"Any sufficiently complex technology is indistinguishable from magic."