As an example to the already given explanations, I can give this: I'm running a custom compiled 2.6 kernel (untarred to /usr/src/linux) but I have 2.4 headers. I can of course install drivers etc for 2.6, but I can't compile Ekiga (more accurately, its dependence pwlib) because it requires the V4L2 interface of the 2.6 kernel; for that, you have to install the 2.6 headers.

Edit: I meant to say, "I have 2.4 headers", corrected it.

What a co-incidence. I have been building kernels under /usr/src since Slackware 9.1 (or was it 9.0?? ) was released and have never had one problem.
Exactly. I have two devices which require out-of-tree modules. A Netgear Wifi card (Madwifi modules) and an NVidia graphics card. They've always worked for me with a custom kernel compiled under /usr/src. I also use a lot of custom-compiled software. Never had any issues compiling under Slackware with this set up.

I could (and most likely DID) have done something wrong, but when I started playing w/making my own kernels, and removed the "/usr/src/linux" symlink that normally points to slackware's 10.2/2.4.31 default kernel; and then re-made a new symlink that pointed to my new kernel, I found that additional kernels over and above the one I made were no good or wouldn't even make for me. And I found that making my own packages for other app's were glitchy or wouldn't compile either.

I'm now doing a hybrid of what linus said, tho I dont like the idea of leaving my kernel in home, and I've had no problems. To each his own I guess

Idem

Idem

Eric

I wonder how many Slackers put the kernel source in /home vs in /usr/src...

Okay, here we go
http://www.linuxquestions.org/questi...d.php?t=482751

Indiana Department of Environmental Management?

Nope... Dutch for 'same here'

guess it would help to speak Dutch eh?

Thanks.

Actaully it's latin according to many, but I think it really goes back to roman law, basically 'of same mind' but used to be in legal agreement.

Now if we can just translate Alien Bob's wiki jpeg that would be neat

Old Fogie:

http://www.jargon.net/jargonfile/b/blinkenlights.html

I used to have a real good English translation, but alas, I kept
it in /usr/src/linux rather than /home/goodness; and one night
while upgrading Slackware it got overwritten.

Yeah but that is not dutch... it is based on deutsch (german) though... this sums it's origin up quite well: http://www.answers.com/topic/blinkenlights

Cheers, Eric - and laudum to Old_fogie for recognizing the latin.

True, I think it is Latin, but poster was from the Netherlands and there we use it as well as an ordinary word :-)

Old Fogie,

Here's a better translation into English you and I can understand:

Blinking Lights

hahahahaha that's really funny, I bookmarked that one

hehe i made a background http://www.unrealize.co.uk/images/blinken.gif

should keep the red necks away