|
How often does this need arise ?
How often does the need arise to compile your own Kernel and why ? I had a few people suggest this to me. I am interested in learning this. However, for the average user I feel that this is quite a demanding task.
Thanks. Vijay |
Why did the "a few people" suggest it to you? What can't you do that you want to do? What do you want to do that you think that you can't? I don't think that there is any real reason to recompile - unless you are lacking something.
|
Quote:
Vijay |
Well, what is the problem... if it is already in a thread here, then please link to it. Personally I have never needed to recompile my kernel. I've done so a few times for the 'fun' of it. I thought I needed to a while ago... to do with my TV card, but it turns out I just needed to play around with the modprobe arguments.
|
Here is the thread as requested. I am just curious if the need to compile your own kernel occurs often. That is all.
Vijay http://www.linuxquestions.org/questi...threadid=97099 |
there are a lot of good reasons to compile your kernel. i recommend it highly. first off, if u do modprobe -l u'll get this huge list of all the modules compiled with the default kernel. compiling your own kernel allows u to get rid of anything unneccesary. also, if u ever need anything u don't have, u'll know how to add the drivers to your kernel. also, i recompile everytime a new kernel comes out. it helps u to understand how things work a lil better. eesteven sed u don't really need to do it unless ur lacking something, but also it's great to do if u have more than necessary.
|
What happens if you have a lot of extra stuff on your Kernel ? Thanks.
Vijay |
There's really no harm in having extra stuff compiled into your kernel. It increases the memory used by the kernel a bit, but that's hardly an issue unless you're trying to run Linux on an old machine with very little RAM. The modules that eltongeoff mentions are pretty harmless; modules are things that you can load if you need them, but skip if you don't. Anything that's listed by modprobe -l or lsmod is probably stuff you need anyway; there are hundreds of other modules that aren't loaded and so aren't wasting any resources other than a little hard drive space.
The reason(s) I've recompiled include: To try to streamline my kernel a bit to make it run faster or more efficiently. I have gotten my machine to boot faster by doing it, but I don't notice any performance differences. I also compiled a custom kernel to try to get Slackware and X working on a 4MB laptop, but that's hardly the kind of thing everyone needs to do. I've very occasionally needed to compile a newer kernel in order to enable some obscure piece of hardware, but if all your hardware is working okay, that won't be an issue for you. Anyway, to answer your question: Unless you encounter a specific problem that really requires that you compile/recompile your kernel, I would not worry about it. It can be one of the hardest and most stressful things to learn about Linux at first, and a royal pain in the arse if it goes awry. I remember when I was first learning Linux, almost every question I asked was answered with "oh, just recompile the kernel." Of course, nothing sounds more terrifying to someone who barely knows anything about Linux! Eventually, I did compile my own kernel, and have compiled many more since then, but don't do it until you think you're ready. |
Quote:
As a solution if recompiling the kernel is suggested, for a newbie this is quite a task indeed. No wonder I still hear that Linux has a long way to go before the small user can use it. If just the boot time is decreased then I can live without it. Down the road I agree this will be helpful and good to know. For now I feel that I should know more about adding and removing drivers or other Kernel components. Any info. in this regard welcome. Vijay :newbie: |
| All times are GMT -5. The time now is 09:05 PM. |