Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
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.
Is there a universal tool for probing hardware and determing which features can be safely removed from the .config file used in kernel building? Today I removed a lot of features that seemed to me unused using the menu xconfig command, but the new kernel didn't boot. So I've found myself choosing between 2 evils - there's dozens and hundreds drivers I wouldn't need (telephony, amateur radio, video cards I don't have etc etc etc) but I don't know exactly about many of these features whether they're relevant for my hardware or not, whether I should them remove. The standard device probing program on my Ubuntu 6 doesn't help much. So at the moment I'm compiling a new kernel with all this load of stuff set by default, but it sucks a bit that I'm forced to using drivers I might not need at all. Doesn't anyone know any kind of a tool that could resolve this problem?
If these extra drivers are compiled as kernel modules, as most (just about all) of them are usually by default, then there's really no problem. The only downside is a little extra disk space storing them and a little longer compile time when you redo your kernel. Your system will not run slower, or use more memory, because of a few unused modules laying around. You will use a bit more disk space to store them, but it's usually insignificant in the grand scheme of things. You can get rid of the things you OBVIOUSLY won't be needing when you compile the kernel, but if it's not 100% obvious then I'd say just let it compile (as a module). Your CPU needs to work up a good sweat every now and then anyway! (To keep the thermal paste conducting well )
Distribution: Distribution: RHEL 5 with Pieces of this and that.
Kernel 220.127.116.11, KDE 3.5.8 and KDE 4.0 beta, Plu
No tool I know of. The Docs within the kernel source explain what many of the modules that can be built will work with. Easiest way if unsure then make as module. Like haertig says it will take up more space but will not impact on performance because if not needed then it is not loaded.
Thank you Hangdog42!!! This is tool is practically what I needed!!!
Yes, you are right, guys, about compiling things as modules, but you always want your system to be perfect and kernel being compiled some ten minutes shorter...