From: romeusmeister@gmail.com (Roman Storozhenko)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Update a newly-created '.config' file with some predefined values
Date: Wed, 31 May 2017 10:26:22 +0300 [thread overview]
Message-ID: <20170531072622.GA10404@home> (raw)
In-Reply-To: <20170530092834.GA19566@home>
On Tue, May 30, 2017 at 12:28:34PM +0300, Roman Storozhenko wrote:
> 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
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.
prev parent reply other threads:[~2017-05-31 7:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-30 9:28 Update a newly-created '.config' file with some predefined values Roman Storozhenko
2017-05-30 15:57 ` valdis.kletnieks at vt.edu
2017-05-31 7:26 ` Roman Storozhenko [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170531072622.GA10404@home \
--to=romeusmeister@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.