DebianThis forum is for the discussion of Debian Linux.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Now assuming i understand this ok, if a security risk was found in this kernel, a new one would be released, maybe 2.6.8-2. And then i could download and install this, easy enough.
But what if i have customised my own kernel from the kernel source. How would i go about updating it, or would i have to download it and go through the whole menuconfig again to recompile or something?
If so, would the .config file for 2.6.8-1 be usable with a future 2.6.8-20?
you can get the new source then copy your old .config file into the directory and use "make oldconfig" this should keep your old setting and ask you for any new settings that the kernel has that wasn't specefied in the old kernel.
Originally posted by kola Ah that makes sense. I'd hate to have to edit every option every time a new kernel came out.
On this old machine a recompile takes almost an hour.
will after you have the config file setup you will still have to compile, and I do remember that when I had linux on a slow machine it would take hours to compile, then you get an error and have to start over. The good thing though is once you have a kernel thats up to date and properly configued then there is no need to update it for sometime. Most people will actually waite 6 months or a year and see how a new kernel release is doing before they trust to upgrade. So there is no need unless the new kernel supports something on your box that you need and can not get it to work with old kernel.
If you just want to play though, I should say once I got a new computer and put linux on it, the compiling only takes 15 minuts are so, so thats defiantly something to look at, linux isnt just for old machines
well I still consider myself a newbie to linux so maybe your asking the wrong guy. But I think with the speed of todays computers your not going to notice a real differene. I configured my kernel manually just so I could learn more about it, but now looking back on it if say my network card failed I would have to reconfigure my kernel again because it doesnt have the ability to use any other enthernet cards. The only real reason to configure your kernel is for special needs that the default doesnt offer, or if you have a specialized system that say your wanting to use as a a router or something then you could make the kernel a lot more secure with not having some of the features enabled that could cause a vunerbility and you can reduce the size of the kernel. But from my experience, a basic install with the default kernel works on most desktops
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.