Is it possible to use "make menuconfig" ONLY for new options after a Kernel upgrade ?
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.
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.
Is it possible to use "make menuconfig" ONLY for new options after a Kernel upgrade ?
Instead of doing
make oldconfig
make menuconfig
is there any other make rule so that after a kernel upgrade to use something like "make menuconfig" but only for new options from the new kernel version ???
if there is a way with "make xconfig" please refer to it
Yeah, you really do need to review the whole set of options when you upgrade or recompile ... some "old" options might be inconsistent with or superseded by "new" ones, and also there might be some "new" stuff that you really don't want or need to use. It is possible to request a set of kernel options that results in a kernel that will not compile or install properly.
Always...
Keep a copy of every .config that you have ever used, or ever attempted. Keep it in an un-hidden file "somewhere else," outside of the main build-tree. Make the copy after you've finished making the config, and before you install from it, just so that you don't lose or misplace anything.
Change the name of each kernel, so that you do not over-write the one that you are running now.
Use diff to compare config-files to make sure that you made only the changes that you intended.
Keep a diary... do not rely upon your ... your ... oh dear, now what was I just saying? ...
TO be honest, I can't even imagine a way to handle oldconfig in a GUI. It would essentially just move from old setting to old setting... Would you want it to display only a menu of the new options?
Originally posted by Matir TO be honest, I can't even imagine a way to handle oldconfig in a GUI. It would essentially just move from old setting to old setting... Would you want it to display only a menu of the new options?
just to config them in a way that i could use help to read more about it than having to go through the menuconfig process and search for "NEW"
When doing oldconfig, you CAN supply '?' as the result, and that will display the help information for the choice, then prompt you for Y/n/? again. Or Y/m/n/? or whatever.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.