From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] https://wiki.gentoo.org/wiki/Traffic_shaping
Date: Mon, 23 Nov 2015 22:47:35 +0200 [thread overview]
Message-ID: <56537B67.2040902@gmail.com> (raw)
In-Reply-To: <87si3we9zz.fsf@heimdali.yagibdah.de>
On 23/11/2015 22:31, lee wrote:
> 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?
>
By using a tool that *does* show you the options and how to make them
available.
The kernel devs have no desire to hold anyone's hand; they assume
(correctly IMNSHO) that anyone configuring a kernel knows what they are
doing and knows the tools to use. With that approach, sometimes the user
runs into things they can't find, and it's an acceptable price to pay.
--
Alan McKinnon
alan.mckinnon@gmail.com
next prev parent reply other threads:[~2015-11-23 20:48 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
2015-11-23 20:47 ` Alan McKinnon [this message]
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=56537B67.2040902@gmail.com \
--to=alan.mckinnon@gmail.com \
--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