From: "Robert P. J. Day" <rpjday@mindspring.com>
To: Adrian Bunk <bunk@stusta.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH][RFC] Create a top-level "Space-critical features" menu.
Date: Tue, 8 May 2007 12:14:33 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0705081205440.8750@localhost.localdomain> (raw)
In-Reply-To: <20070508085654.GG4226@stusta.de>
On Tue, 8 May 2007, Adrian Bunk wrote:
> On Tue, May 08, 2007 at 04:06:30AM -0400, Robert P. J. Day wrote:
> >
> > i've always hated that lower-level menu under "General setup":
> >
> > Configure standard kernel features (for small systems) --->
> >
> > which buries the choice of de-selecting features to save space one
> > level down without really explaining what it's all about. so i just
> > shifted all of that up to the top under what i think is a more
> > meaningful name.
> >
> > this patch is also why i asked earlier why top-level menu entries
> > have no "help" text -- because, in this case, it would be useful for
> > someone looking at the config screen to see that choice and be able to
> > ask, "hey, i wonder what *that's* all about", and get help along the
> > lines of:
> >
> > "these features are normally selected but, if you're strapped for
> > space, such as with embedded systems, you might consider turning some
> > of them off. if space isn't an issue, you might as well just leave
> > them as they are." (or something like that.)
> >...
>
> I'm against it:
>
> I don't have numbers, but I'd expect the vast majority of people
> building kernels to be people with low kernel knowledge building for
> an i386/x86_64 system.
i agree. but a number of people have already suggested that that
lower-level menu
"Configure standard kernel features (for small systems)" --->
is not well-designed. and the very people you're talking about will
see that and not be quite sure what it represents. and they
*certainly* won't realize that *not* selecting it will have
consequences in other menus.
that particular menu is confusing for a number of reasons:
1) it's badly named
2) it has no help to explain it
3) even if you don't select it, it will still have some sub-menu
entries, which is non-intuitive
4) it's not at all clear that, if you don't select it, other possible
config entries all over the source tree won't be available.
> OTOH, people developing embedded systems are most likely more
> familiar with kernel internals.
i'm betting even embedded people might not understand what's going on
there. it's particularly confusing since, if you choose that option,
you will suddenly see a number of additional "small system" features
you can turn off, but there's no indication that options all over the
tree are suddenly becoming visible.
note: i have no problem with some kind of overall, top-level option
that does this sort of thing. i just don't think the current
technique is the right way. in fact, i think it's awful, and i'd love
to see it made more obvious.
rday
--
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA
http://fsdev.net/wiki/index.php?title=Main_Page
========================================================================
next prev parent reply other threads:[~2007-05-08 16:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-08 8:06 Robert P. J. Day
2007-05-08 8:21 ` Thomas Gleixner
2007-05-08 8:27 ` Robert P. J. Day
2007-05-08 8:37 ` Thomas Gleixner
2007-05-08 8:41 ` Robert P. J. Day
2007-05-08 9:21 ` Jan Engelhardt
2007-05-08 13:03 ` Stefan Richter
2007-05-08 16:19 ` Robert P. J. Day
2007-05-08 20:22 ` Matt Mackall
2007-05-08 8:56 ` Adrian Bunk
2007-05-08 16:14 ` Robert P. J. Day [this message]
2007-05-08 20:10 ` Matt Mackall
2007-05-08 20:34 ` Robert P. J. Day
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=Pine.LNX.4.64.0705081205440.8750@localhost.localdomain \
--to=rpjday@mindspring.com \
--cc=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®