From: lee <lee@yagibdah.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] https://wiki.gentoo.org/wiki/Traffic_shaping
Date: Mon, 23 Nov 2015 21:31:26 +0100 [thread overview]
Message-ID: <87si3we9zz.fsf@heimdali.yagibdah.de> (raw)
In-Reply-To: <20151123133009.GU3539@ns1.bonedaddy.net> (Todd Goodman's message of "Mon, 23 Nov 2015 08:30:09 -0500")
Todd Goodman <tsg@bonedaddy.net> writes:
> * Peter Humphrey <peter@prh.myzen.co.uk> [151123 07:15]:
>> On Monday 23 November 2015 12:11:36 Peter Humphrey wrote:
>> > On Monday 23 November 2015 12:29:42 lee wrote:
>> > > Neil Bothwick <neil@digimed.co.uk> writes:
>> > > > Grepping .config proves nothing. If a requirement of the option is not
>> > > > set, the option may not appear in .config. The only reliable test is
>> > > > the
>> > > > search facility in make *config.
>> > >
>> > > Search facility?
>> > >
>> > > I only use menuconfig and often times, it's difficult to find a
>> > > particular option I'm looking for.
>> >
>> > Touch the / key, then enter the option name minus the CONFIG_ prefix. Case
>> > is not sensitive.
>>
>> I forgot to add that if more than one result is returned, they're numbered.
>> Then if you hit the number key of the one you want, you go straight to it.
>
> And when you exit from reading that selection you get back to the
> results list.
>
> It's pretty slick and sure beats looking where I "think" it should be or
> grepping KConfig files.
Wow, that might save me a lot of time :)
And qdisc is extremely well hidden, I'd never have found that. It
doesn't show up unless other options are enabled: You have to know
exactly what you want to enable before even knowing that it's there.
How are we supposed to be able to configure a kernel when we can't even
see the available options anymore?
next prev parent reply other threads:[~2015-11-23 20:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-19 14:53 [gentoo-user] https://wiki.gentoo.org/wiki/Traffic_shaping lee
2015-11-20 11:47 ` Mick
2015-11-22 23:14 ` lee
2015-11-22 23:39 ` Neil Bothwick
2015-11-23 11:29 ` lee
2015-11-23 11:35 ` Alan McKinnon
2015-11-23 12:11 ` Peter Humphrey
2015-11-23 12:14 ` Peter Humphrey
2015-11-23 13:02 ` Emanuele Rusconi
2015-11-23 13:30 ` Todd Goodman
2015-11-23 20:31 ` lee [this message]
2015-11-23 20:47 ` Alan McKinnon
2015-11-25 16:28 ` lee
2015-11-23 23:08 ` Neil Bothwick
2015-11-24 6:26 ` Mick
2015-11-24 8:49 ` Neil Bothwick
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=87si3we9zz.fsf@heimdali.yagibdah.de \
--to=lee@yagibdah.de \
--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