SlackwareThis Forum is for the discussion of Slackware Linux.
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 have a question with regards to the kernel. I am running Slack 10.0 with a custom 2.6.8 kernel. The question is, if I save the entire '/usr/src/linux' directory onto a CD or something, can I use it again with a new installation. I mean, I don't want to compile the entire kernel again. So, can I store the compiled kernel tree, reinstall slack, and do a 'make' 'make modules_install' from the saved source?
If you just need the kernel, its in /boot. also save the corresponding /lib/modules/[kenr ver]
One of the reasons why you would want to have source+compiled *.o's etc. is to shorten the time it takes you to compile again. (like when you forgot to include a module, you do "make xconfig" and "make" "make modules_install" But, i don't think that is what you are trying to get.
But the kernel image that is present in '/boot' is also present in '/usr/src/linux/', right. My questions is if I store the entire '/usr/src/linux' directory and after copying it back, if I do 'make' 'make modules_install', will it result in lesser compilation?
Generally it can be a bad idea because you could have different libraries or compiler versions on a different machine. However, if you're talking about switching to a clean install of the EXACT same system, you should be fine.