make menuconfig: saves a larger file then original after save done when no changes made.

Devyn · 04-10-2016, 01:37 PM

I'm wondering why the .config file size is different when I save after using .config? I made no changes to the .config file. I would then expect it to be saved with same size. The options selected in the generated config file is not what I picked. Doesn't seem menuconfig uses the .config file I copied, but a copy from elsewhere:

Quote:

2332 -rw-r--r--. 1 root root 107139 Mar 22 18:45 .config.old
2442 -rw-r--r--. 1 root root 139490 Apr 10 14:32 .config

Anyway to change this and ensure menuconfig uses the .config I copied in?

Cheers,
DH

Keith Hedger · 04-10-2016, 03:21 PM

If the old menuconfig file yoh copied is from a different kernel version the new menuconfig will have slightlt differernt options, and hence a slightly different size.

Devyn · 04-10-2016, 06:20 PM

It's the same version. I'm recompiling a custom one off the same Kernel version base.

Cheers,
DH

Keith Hedger · 04-11-2016, 04:27 AM

try using diff on the two versions to see where the changes are

sundialsvcs · 04-11-2016, 06:58 AM

It is always a good idea to make backup copies of the hidden .config file, "dated and stored, say, in /root/linux_configs," so that you can always and immediately see what the changes are, and to revert to previous known-good copies.

Devyn · 04-11-2016, 06:39 PM

I did run a diff, even though I copy the .config to the folder I'm running make menuconfig from, then despite making NO changes to the configuration, on save the resultant file is 300KB bigger then the original file. diff is pages and pages long but I made no changes in menuconfig, I just saved it as a test to show changes roll in that have not been made.

So where is it getting the config file from?

Cheers,
DH

jpollard · 04-15-2016, 03:40 PM

Not seeing what the diff shows, I would guess at extra comments...