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.
As a newbie I intend to undestand what goes wrong with a certain kernel configuration procedure that starts with
# make menuconfig
and ends with
# make modules
Of course I want to keep as to be functional the actual "satisfactory" configuration of my system. Since a newbie I would appreciate any comment on my plan to work.
1) Make a directory, say /Test, in /usr/src and downoad kernel sources in it.
2) Enter /usr/src/Test as root and do all the work in that directory.
3) Limit myself to the first needed feature (in customizing the kernel) and then apply
# make modules
to this limitating stage. If things go OK, then proceed further to the second feature (and so on) untill occuring the error message.
After learning the bug, undo (?) all the work and finally delete the /Test directory.
Could you please comment on:
(a) How should the "undo" work look like.
(b) What is the difference between source files called as <*kernel*.rpm> and source files called as <*kernel-devel.rpm>: which type of the two should I download to work with?
(c) Is it true that, during my work, Fedora Core 4 will automatically provide me with a "Test" item in the booting menu? And if positive, will my "undo" procedure also undo this booting item, or should I manually remove it out of GRUB?
Grateful thanks for any opinion!
form one newb to another .. so long as you don't delete your old kernel it will still be there. If your kernel fails you just have to ln -s the config/systemmap/linux files/directories back to the way it was. and don't delete the kernel info from your boot loader, just add to it
You still have your boot disk you created when installing right? be sure you back up first
and compiling a kernel isn't as scary as it sounds, so long as you know what hardware you have and have a good tutorial you should be good.
Last edited by Furlinastis; 08-04-2005 at 12:33 AM.