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.
If the kernel is compiled with support for a certain feature/hardware (it will be marked with a * in menuconfig), then yes, the size of the kernel increases accordingly. If you just add support as a module (marked with a M), the kernel size is not increased. Some modules will be loaded at boot, so it isn't always necessary to edit /etc/rc.d/rc.modules. However, if you have a module that you need loaded and it does not load by default, then uncommenting it or adding a line for it in rc.modules will usually suffice.
Is it possible to compile and install single module (which was completely missed before) without recompiling and reinstall all modules? Maybe it can be done by inserting parameter (module name or something) to "make modules" and "make modules_install"?
This is my first time I'm trying to recompile a kernel (cuz kde 3.1 takes about 10 seconds just to start up applications and I don't like other guis). I downloaded slackware online and burned it to cd, then did full install (with all applications etc.), but now when I'm trying to follow your guide and you mentioned going to /usr/src/linux/Makefile with text editor, but when I go to /usr/src the only folder there is rpm (and no files there either), after this I searched my disk for makefile and found about 40 of them (and I have no clue which one is the one I need), could someone help me? Thanks.
thanks, I've recompiled my kernel, and now my KDE 3.1 opens everything up instantly (used to be up to 20 seconds before), I didn't know kernel would have this much effect on KDE. But there is another problem now. Linux no longer supports sound (and it even gives an error message about that when it boots up) and the internet no longer works. For the internet I think I know what the problem might be, I didn't think I would need to share files across computers so I disabled file sharing with other computers and from other computers, but since I use a router it probabaly thinks of my router as a computer too. So I think I can fix the internet (I hope), but I have no clue what to do about the sound, I think I only disabled one sound option that said I should type lspci -n to see if I was using it, and when I typed it it said that I wasnt using that thing, os I said N for it.
Originally posted by timezero Great guide. thanks.
However, my guide does not include 'make menuconfig' 'make clean' and 'make' but 'make mproper' and 'make config' So I was wondering if anyone could tell me the difference?
make mproper is like an aggressive make clean
make config is make menuconfig but text based.
On Another Note:
If, like me, you can't be arsed to deal with modules. Just compile them directly into the kernel (e.g '*' and not 'M' in make menuconfigs selection boxes).
You loose the advantages of dynamically loading and unloading modules/drivers. But I have no need to do that :-)
And to get detailed information on an option in make menuconfig just press "SHIFT + ?" when the option is selected.