Pierre Labastie wrote:
Le 06/12/2014 23:58, Bruce Dubbs a écrit :
Pierre Labastie wrote:
Le 06/12/2014 15:50, Ken Moffat a écrit :
On Sat, Dec 06, 2014 at 12:08:39PM +0100, Pierre Labastie wrote:
Hi,
I think I am done with the uniformization of the layout for Kernel
Configuration instructions.
Question: Should we add a paragraph to "Conventions Used in this Book"?
What I
fear is that in some cases, depending of other selections in the kernel
configuration menus, angle brackets (<*> are replaced by braces {*}, or even
dashes -*-, or some options are not visible, so users might be confused. It
might be nice to explain that, and also the difference between <*>, <*/M>,
and
<*/M/ >.
Regards
Pierre
Thanks for doing that. Adding a paragraph sounds good: in 'make
menuconfig' as I am sure you know, you can use '/' to search for a
config symbol. The output will tell you how things on which that
symbol relies are set.
ĸen
Yes, that should be explained. but sometimes, "things on which that symbol
relies" is 10 lines long or so, which is rather confusing...
I guess it may be a good idea also to explain how to access the general
instructions (clicking "help" when the cursor is on a non selectable menu
line). Hmm, not sure what I write is clear. I mean, if the cursor is on a line
like this:
-----------
some menu title without a selectable box on the left --->
-----------
and you click "help", then you get the general instructions.
Different topic: guess you all know this, but I just realized that there is
"make nconfig", which is close to "make menuconfig", but with improved help
(acessible through function keys). Do you think it should be mentioned?
Well, maybe not in the "convention" page.
It should go in the LFS linux page, but I think saying that 'make help'
provides a lot of options would allow users to select what they think is best.
-- Bruce
You're right, LFS linux page is the right page. What "make help" says:
-----------
nconfig - Update current config utilising a ncurses menu based program
menuconfig - Update current config utilising a menu based program
-----------
which is misleading (menuconfig actually uses ncurses, and the improved help
with nconfig is not mentioned: this one of the reasons, besides lack of
curiosity, which made that I never used nconfig before).
Maybe just add a sentence saying that nconfig is recommended rather than
menuconfig, because the help system is superior?
Honestly, I haven't used nconfig before either, but I like it. Have you
tried it with:
make LANG=<host_LANG_value> LC_ALL= nconfig
We do mention oldconfig, but no other methods.
What do you think of the following?
"There are many ways to configure the Linux kernel. To see a list of
all the methods run <command>make help</command>."
And then just change menuconfig to nconfig right below that.
Do we need to be more verbose than that?
-- Bruce
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
