public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Tanstaafl <tanstaafl@libertytrek.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Peeve - finding kernel config options
Date: Thu, 27 Feb 2014 12:34:46 -0500	[thread overview]
Message-ID: <530F7736.6050105@libertytrek.org> (raw)
In-Reply-To: <530F74E2.7050401@dmj.nu>

On 2/27/2014 12:24 PM, Dan Johansson <dan@dmj.nu> wrote:
> On 26.02.2014 22:24, Poison BL. wrote:
>> When I search FHANDLE in menuconfig I get:
>>
>>    │ Symbol: FHANDLE [=y]
>>    │ Type  : boolean
>>    │ Prompt: open by fhandle syscalls
>>    │   Location:
>>    │ (1) -> General setup
>>    │   Defined at init/Kconfig:235
>>    │   Selects: EXPORTFS [=y]
>>    │   Selected by: GENTOO_LINUX_INIT_SYSTEMD [=y] && GENTOO_LINUX [=y]
>> && GENTOO_LINUX_UDEV [=y]
>>
>> This clearly states that the prompt you're looking for is a line that
>> says "open by fhandle syscalls" under "General setup"
>>
>> Sure, it's not the absolute simplest interface (i.e. it doesn't give a
>> 'enable this' in the search results) but it does give all the
>> necessary information about a given option to find it (as well as
>> dependencies and their current states, etc). The most likely reason
>> the news item doesn't list the specific "prompt" text (or even the
>> category) is that, across even sub release versions of the kernel
>> those are prone to change (and, at times, drastically) while the
>> actual CONFIG_<name> option tends to be fairly static through time
>> once it exists (even when superseded by new toys, i.e. older
>> IDE/ATA/ATAPI options vs newer PATA options).
>
> But if you press "1" in the example above you will "jump" directly to
> the menu item. Clue --> (1)

And that is by far the HANDIEST tip from this thread... awesome! Thx Dan!


  reply	other threads:[~2014-02-27 17:35 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-26 19:58 [gentoo-user] Peeve - finding kernel config options Tanstaafl
2014-02-26 20:05 ` Neil Bothwick
2014-02-26 21:24 ` Poison BL.
2014-02-26 21:41   ` Tanstaafl
2014-02-26 21:50     ` Neil Bothwick
2014-02-26 22:21       ` Dale
2014-02-26 23:22         ` wraeth
2014-02-27  0:03           ` Dale
2014-02-27  8:50           ` Neil Bothwick
2014-02-27 10:25     ` Peter Humphrey
2014-02-27 17:24   ` Dan Johansson
2014-02-27 17:34     ` Tanstaafl [this message]
2014-02-27 19:12       ` Poison BL.
2014-02-27 19:41         ` Dale
2014-02-27 17:58     ` thegeezer
2014-02-28  2:31       ` [gentoo-user] " walt
2014-02-28 10:11         ` thegeezer
2014-02-27 19:38     ` [gentoo-user] " Alan McKinnon
2014-02-28  0:29       ` Peter Humphrey
2014-02-27 19:49     ` Samuli Suominen
2014-02-27 19:59       ` Samuli Suominen
2014-02-27 20:09         ` Tanstaafl
2014-02-27 20:33     ` Neil Bothwick
2014-02-27 21:01       ` Samuli Suominen
2014-02-27 22:51         ` Neil Bothwick
2014-02-26 21:39 ` [gentoo-user] " »Q«
2014-02-27  6:04 ` [gentoo-user] " Alan McKinnon
2014-02-27 10:40   ` Andrew Savchenko
2014-02-27 11:00   ` thegeezer
2014-02-27 18:24   ` [gentoo-user] " Grant Edwards
2014-02-27 18:32     ` Grant Edwards
2014-02-27 19:47       ` Alan McKinnon

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=530F7736.6050105@libertytrek.org \
    --to=tanstaafl@libertytrek.org \
    --cc=gentoo-user@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox