I compile them in my home directory because I don't know enough about it to argue with linus.

I always do /usr/src, but it really doesn't matter; you could compile it out of /home and have the same results.

I suppose the argument could be made that, if you are working on a multi-user system, it would be better to have the source located in /usr/src as any user on the machine would be able to compile software against it (but with normal default permissions, would not be able to modify the kernel source). But on a single user machine, which the vast majority of Linux users are running now, having the kernel source in your /home won't change anything so long as the symlinks point to the right location.

I when I compile a kernel it is in order to apply the RT-Patch, i've only done this a few times but usually I create a working directory named with the Kernel's version string. Yeah I guess I do this in my home directory; /home/user-name/RTWORKING/linux-2.XX.XX.X-686-rtX. I've had my share of issues while cooking kernels, but so far none have been related to where I do the patching/build process

I compile it in my home directory, and the source is also stored there. This is just easier if you're going to use git. I don't want to use git as root in some root directory. I've never had any issues with doing this.

I always do that on my /home-partition, just because it is a fast RAID 0-array. May be I should do it on a RAM-disk next time.

I have a kernels directory in home where I keep the last proven kernel source (from experience) and the latest git checkout. I always build in the /home directory. It just makes life easier.

I've only done it once.
And I compiled it in /usr/src because I don't know enough about it to argue with Alien Bob.
http://alien.slackbook.org/dokuwiki/...kernelbuilding

You could say I do it in /home, because I've only ever done it a few times (not counting retries ), and each time I've used the ABS to automate it (save for kernel config options; edited the PKGBUILD to run make nconfig so I could customize it). I keep anything I build from the AUR or ABS tree in directories in /home/mrcode/AUR and /home/mrcode/ABS, respectively.

Hi,

I always use /tmp as a normal user (not root).
The reason is that I've to install the kernel as root and I don't want to use rootpermissions within my homedirectory and I don't want to overwrite the kernelsources in /usr/src before the new kernel is ready to use.

Also it seems to be recommended for Slackware to use /tmp, but I'm not sure.

Markus

I wouldn't put or leave anything important in /tmp, it's meant to be expendable.

Well, when the kernel is built, I copy it (as root) to /usr/src and install it afterwards. Slackware doesn't automatically whipe the /tmp directory (other distributions do).

Markus

If you move it out after compiling, then it's ok.

I originally used that guide. But running as root was annoying.

I do all compiling in /tmp/, which is a tmpfs mount on my systems.

Hopefully you have plenty of RAM.