From: Randy Dunlap <randy.dunlap@oracle.com>
To: Yihe Chen <yihect@juliantec.info>
Cc: linux kbuild list <linux-kbuild@vger.kernel.org>
Subject: Re: config help
Date: Mon, 01 Nov 2010 09:31:48 -0700 [thread overview]
Message-ID: <4CCEEB74.9010809@oracle.com> (raw)
In-Reply-To: <942B93F2162249F3B4CE745DAF6FD9E1@PC200810081817>
On 10/29/10 18:24, Yihe Chen wrote:
>> On Fri, 29 Oct 2010 20:01:55 +0800 Yihe Chen wrote:
>>
>>> Where to find information or helping stuff or usage info on those config
>>> tools, like conf/gconf etc.
>>
>>
>> Begin with the README file in the top-level directory of the linux
>> source tree.
>>
>> For menuconfig: use ?
>>
>> For nconfig (in recent kernels): use 1 or <F1>
>>
>> For gconfig: click on Help
>>
>> For xconfig: click on Help
>>
>> There is also some help info in Documentation/kbuild/kconfig.txt .
>>
> /
> First, thanks for your reply. I'm reanding scripts/kconfig/Makfile, and
> tacking
> notice of some options used with conf tool, like -r -y -n -m -d and -D.
What kernel version are you looking at? Something before 2.6.36 ?
I ask that because in 2.6.36 and later, the config command line tool only
uses long option strings (like --oldconfig), not short option strings
(like -o).
Anyway, in 2.6.35, scripts/kconfig/Makefile is fairly clear on those
short option strings:
-o oldconfig
-s silentoldconfig
-r randconfig
-y allyesconfig
-n allnoconfig
-m allmodconfig
-d defconfig
-D filename use filename as default configuration
> Now I havn't a clear understanding on those meaning. I want to look some
> text notice
> about this. Though I could find info from scripts/kconfig/conf.c, I
> don't want to
> befoul my fingers by the fucking code currently.
--
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2010-11-01 17:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-29 12:01 Yihe Chen
2010-10-29 17:07 ` config help Randy Dunlap
2010-10-30 1:24 ` Yihe Chen
2010-11-01 16:31 ` Randy Dunlap [this message]
2010-11-01 17:41 ` Arnaud Lacombe
2010-11-01 17:46 ` Randy Dunlap
2010-11-01 18:08 ` Arnaud Lacombe
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=4CCEEB74.9010809@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=yihect@juliantec.info \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox