archive mirror
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <>
To: John Bradford <>
Subject: Re: some kernel config menu suggested tweaks
Date: Thu, 24 Jul 2003 14:49:07 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.53.0307241437260.21205@localhost.localdomain> (raw)
In-Reply-To: <>

On Thu, 24 Jul 2003, John Bradford wrote:

> > 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

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.


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

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-24 18:45 some kernel config menu suggested tweaks John Bradford
2003-07-24 18:49 ` Robert P. J. Day [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-07-26 15:20 John Bradford
2003-07-24 19:10 John Bradford
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 14:33     ` Tomas Szepe
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.53.0307241437260.21205@localhost.localdomain \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).