Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
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.
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.
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.