Alan McKinnon <alan.mckin...@gmail.com> writes: > On 23/11/2015 22:31, lee wrote: >> Todd Goodman <t...@bonedaddy.net> writes: >> >>> * Peter Humphrey <pe...@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 <n...@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.
Which tool is that? > 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. Assuming that when someone wants to do something they already know what they are doing and not allowing them to learn by hiding what there is to know leads to nobody being able to do anything. Ask around: How many people do know exactly what they are doing when they are configuring a kernel? You only need to find one who doesn't to prove the supposed assumption of the kernel developers wrong. And I never really knew what I was doing when I configured a kernel. Do you? Who does?
