Upgrading the kernel - Quick question about the .config
SlackwareThis Forum is for the discussion of Slackware 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.
Upgrading the kernel - Quick question about the .config
Hi there!
I'm about to upgrade the kernel to the latest stable version, and I am wondering if I could just use the .config file found on the ftp mirrors under /Slackware-13.01/kernels/hugesmp when compiling?
I mean, instead of doing it manually using menuconfig.
Robby has posted a generic config file for 2.6.35.4 for Slackware. x86 x86-64. It will be easier than having to answer all the default questions due to changes in the kernel versions from 2.6.33. But to answer the question I would normally do
Code:
make oldconfig
at the very least. Google "alien kernel" for Eric's Slackware kernel how-to.
I usually use the generic-smp kernel's config and do:
Code:
yes '' | make oldconfig
Which updates the config file and automatically chooses the defaults for all new options.
But since Robby has generic configs for the latest kernel, you might as well use those.
Does this actually pipe yes to all the questions? Doesn't that say yes to a lot of defaults that would otherwise be no, and that might very possibly interfere since they are being built INTO the kernel rather than as modules? I generally would do
Code:
make oldconfig
and then just hold down enter to choose the default answer for each new option which is generally "no" and then I do my in-depth checking of new options in menu/gconfig.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.