linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Bradford <john@grabjohn.com>
To: john@grabjohn.com, rpjday@mindspring.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: some kernel config menu suggested tweaks
Date: Thu, 24 Jul 2003 20:10:32 +0100	[thread overview]
Message-ID: <200307241910.h6OJAWnm000706@81-2-122-30.bradfords.org.uk> (raw)

> > > 1) i mentioned this before, i think, but after one deselects
> > >    Power management, should ACPI Support and CPU Frequency
> > >    scaling still be available?
> > >
> > >    the "make xconfig" menu display suggests a submenu 
> > >    structure there, which clearly isn't the case.
> > >
> > >
> > > 2) can all of the low-level SCSI drivers be made deselectable
> > >    in one swell foop?  folks might want SCSI support just for
> > >    generic support and SCSI (ide-scsi) emulation, but have no
> > >    interest in low level SCSI drivers.
> > >
> > >    so it would be convenient to be able to select the generic
> > >    support, and yet not have to deselect low-level drivers
> > >    and PCMCIA SCSI adapter support painfully, one at a time.
> > >
> > > 3) can all of ATM support be deselected with a single click?
> > >    in the same way "PCMCIA network device support" is done just
> > >    above it under "Networking options"?
> > 
> > A lot of these add extra complications for anybody not wanting a
> > 'simple' kernel config.  _Please_ don't re-design everything the same
> > way as the once-simple filesystems menu.
> > 
> > Too much prompting is irritating for advanced users, and they are the
> > people who are likely to compiling the most kernels, rather than
> > sticking with the kernel that came with their distribution.
>
> ok, this one i *am* going to take a stand on -- you're making no
> sense whatsoever, so just put down the keyboard and step back.
>
> all of the above three suggestions are for the purpose of either
> simplifying the current menu structure or making it more consistent
> with the way the rest of the menus are presented.  none of them
> increase the complexity of *anything*.
>
> how the heck can you refer to "A lot of these" in the context
> of three suggestions?  get a grip, dude.
>
> and as the complete rookie who took it upon himself to learn
> the Kconfig structure so i could bring some order to the filesystems
> menu, well, frankly, i *like* that structure, and i haven't heard
> any complaints.  you seriously think the original structure was
> *clearer*?
>
> since i don't have the ability to actually hack down at the code
> level, i figured i could still contribute by making it easier for
> newbies like myself with simpler and more consistent menus.
> apparently, this might not be worth the effort after all.
>
> thanks ever so much for the encouragement.

It's not personal, please accept my apologies if it seemed that way,
it's just a co-incidence that the couple of things I don't like were
done by you :-).

The point I'm trying to make is that if you've been using Linux for
years, all these 'clean-ups', that might seem to make things easier
and more organised for new users, really just add extra levels of
indirection for experienced users.

The filesystem menu, for example, I could previously just skip down in
make menuconfig, selecting and deselecting what I wanted.  Now, I have
to go in and out, and in and out, just to see what's selected and
what's not.  Sure, it might look nice to a new user who doesn't like
to see a lot of options they don't necessarily understand, but it
wastes the time of more experienced users.

Oh well, I'll just go back to the:

vi .config
make oldconfig

kernel configurator.

:-(.

John.

             reply	other threads:[~2003-07-24 18:45 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-24 19:10 John Bradford [this message]
2003-07-24 19:53 ` Petr Vandrovec
2003-07-26 12:52 ` Tomas Szepe
2003-07-26 13:07   ` Robert P. J. Day
2003-07-26 13:19     ` Loading of modules fails while using kernel 2.6.0-test1 Manjunathan Padua Yellappan
2003-07-26 13:29       ` Felipe Alfaro Solana
2003-07-26 13:34         ` Manjunathan Padua Yellappan
2003-07-26 14:33     ` some kernel config menu suggested tweaks Tomas Szepe
  -- strict thread matches above, loose matches on Subject: below --
2003-07-26 15:20 John Bradford
2003-07-24 18:45 John Bradford
2003-07-24 18:49 ` Robert P. J. Day
2003-07-24 17:05 Robert P. J. Day
2003-07-26 12:14 ` Tomas Szepe
2003-07-26 12:30   ` Robert P. J. Day
2003-07-26 13:01     ` Tomas Szepe
2003-07-26 13:45     ` Randy.Dunlap

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=200307241910.h6OJAWnm000706@81-2-122-30.bradfords.org.uk \
    --to=john@grabjohn.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rpjday@mindspring.com \
    --subject='Re: some kernel config menu suggested tweaks' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).