Skip to contentSkip to conversation

Update a newly-created '.config' file with some predefined values

DISCUSSION Roman Storozhenko 2 participants 3 messages May 30, 2017 – May 31, 2017

lore
Share & tools
lore
#0 lore raw

Hello everybody,

I have a host machine and I have a VM machine running CentOS 7 with 3.x. There is a kernel source tree on the host. I have made 'make menuconfig',
populated all options that I want to have in my custom kernel and as a result got a '.config' file. Then I copied a centos-default distro config file from my VM's 'boot' catalog to my host's kernel source tree catalog. So now I have
two files in my source tree: '.config' and '.config.old'. I am able to
see difference between them using the following command:

scripts/diffconfig .config.old .config | less

But is there anyway to update values in '.config' file with the apropriate values from '.config.old' file?
I just want to make sure that all modules will be included in a new custom kernel.

Thanks in advance,
Roman

#1 lore raw
Quoted 3 lines · Roman Storozhenko

Hello everybody,

I have a host machine and I have a VM machine running CentOS 7 with 3.x. Ther

e is

Quoted 3 lines

a kernel source tree on the host. I have made 'make menuconfig', populated all options that I want to have in my custom kernel and as a result got a '.config' file. Then I copied a centos-default distro config fil

e from my VM's

Quoted 10 lines

'boot' catalog to my host's kernel source tree catalog. So now I have two files in my source tree: '.config' and '.config.old'. I am able to see difference between them using the following command:

scripts/diffconfig .config.old .config | less

But is there anyway to update values in '.config' file with the apropriate values from '.config.old' file?
I just want to make sure that all modules will be included in a new custom kernel.

If you want *ALL* modules, just copy the centos-default config to .config

If you want everything from your custom config, copy *that* to .config

If you want to mix-and-match, you're probably going to end up running
diffconfig in one window, and 'make menuconfig' in another, and for each
thing that's different, decide if you want it included or not. Oh, and copy
the config that's closest to what you want to .config to minimize the number
of changes you'll need to do.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 486 bytes
Desc: not available
Url : http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20170530/6f6b5848/attachment.bin

#2 lore raw
In reply to Roman Storozhenko
Quoted 12 lines · Roman Storozhenko

Hello everybody,

I have a host machine and I have a VM machine running CentOS 7 with 3.x. There is a kernel source tree on the host. I have made 'make menuconfig',
populated all options that I want to have in my custom kernel and as a result got a '.config' file. Then I copied a centos-default distro config file from my VM's 'boot' catalog to my host's kernel source tree catalog. So now I have
two files in my source tree: '.config' and '.config.old'. I am able to
see difference between them using the following command:

scripts/diffconfig .config.old .config | less

Quoted 7 lines

But is there anyway to update values in '.config' file with the apropriate values from '.config.old' file?
I just want to make sure that all modules will be included in a new custom kernel.

Thanks in advance,
Roman

I have found a solution. There is a script:

scripts/kconfig/merge_config.sh

It allows to mix many configuration files in a base config. For example:

scripts/kconfig/merge_config.sh -m -r .config
~/kernel/conf_mixins/.config_deb

There are kernel options in .config_deb that include some debugging to the kernel default .config.