From: thegeezer <thegeezer@thegeezer.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Peeve - finding kernel config options
Date: Thu, 27 Feb 2014 11:00:26 +0000 [thread overview]
Message-ID: <530F1ACA.30807@thegeezer.net> (raw)
In-Reply-To: <530ED551.5020200@gmail.com>
On 02/27/2014 06:04 AM, Alan McKinnon wrote:
> On 26/02/2014 21:58, Tanstaafl wrote:
>> Hello all,
>>
>> This is for those of use who to choose to roll our kernels by hand...
>>
>> So, am I missing something?
>>
>> Given the most recent gentoo news item:
>>
>>> # eselect news read 10
>>> 2014-02-25-udev-upgrade
>>> Title Upgrade to >=sys-fs/udev-210
>>> Author Samuli Suominen <ssuominen@gentoo.org>
>>> Posted 2014-02-25
>>> Revision 1
>>>
>>> The options CONFIG_FHANDLE and CONFIG_NET are now required in the kernel.
>> Whenever kernel config options are provided like this, it would be nice
>> if time was taken to provide the path to where they are found.
>
> make menuconfig
> press "/"
> type CONFIG_FHANDLE
> press enter
> profit!!!
>
> [Note the lack of ??? in the list]
>
> works like searching in vi or less
>
>
>
>
>> I had to find the first one (CONFIG_FHANDLE) by:
>>
>> 1. grepping .config, seeing it wasn't enabled,
>> 2. running make menuconfig and searching for 'FHANDLE',
>> 3. seeing it is located in 'General setup',
>> 4. scouring the General setup options, finding no 'FHANLDE' anywhere,
>> 5. finding something in all lowercase named 'open by fhanlde syscalls',
>> 6. enabling this option, saving the modified config,
>> 7. confirming it is now enabled by grepping .config again
>>
>> Sheesh. Really?
>>
>> Would be nice if the news item had something like
>> CONFIG_FHANDLE (General setup > 'open by fhandle syscalls')
>> and
>> CONFIG_NET (still don't know which one this is??)
>>
>> Wackadoo...
>>
>>
>>
>
If you have ncurses you can also do # make nconfig
you can then press F8 to find the category to be in
then you can press / to search -- crucially it will jump to the location
on the screen
next prev parent reply other threads:[~2014-02-27 11:00 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
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 [this message]
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=530F1ACA.30807@thegeezer.net \
--to=thegeezer@thegeezer.net \
--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