From: Bernd Eckenfels <firstname.lastname@example.org>
Subject: Re: why the current kernel config menu layout is a mess
Date: Fri, 25 Jul 2003 03:27:45 +0200 [thread overview]
Message-ID: <E19frN3-00025Iemail@example.com> (raw)
In article <Pine.LNX.firstname.lastname@example.org> you wrote:
> the suboption "Support for paging of anonymous memory".
> might this not go under "Processor type and features",
> where there are other memory-related options?
well, i think it is architecture independend
> "Power management options"
> in addition, though, i'm not sure "CPU frequency scaling"
> belongs here. it might just as well fit under "Processor type
> and features", although that may be nit-picking.
Power Management and System Configuration
could be a better heading
> "Bus options (PCI, PCMCIA, EIAS, MCA, ISA)
> if this is for busses, why aren't the other busses here as
> well? shouldn't USB be here as well?
I think this is concernd with mainboard's main bus only (i2c is an aux
mainboard bus and usb, firewire are device busses)
> "Character devices" (jumping ahead just a bit)
> "Block devices"
> "Multiple devices (RAID and LVM)"
Well, if we go along the line of using unix naming, then MD can be moved ot
block devices, not to filesystems.
> "Fusion MPT"
> hard to believe this deserves its own top-level entry,
> but i could be wrong.
yes, very strange.
> "IEEE 1394"
> it's a bus, right? move it there.
i would suggest to have the section separated into system internal stuff
(cpu, mainboard bus, management bus, memory, apci, ..) and external
interfaces (usb, firewire, legacy/serial/, legacy/parallel, legacy/ps2,
eckes privat - http://www.eckes.org/
Project Freefire - http://www.freefire.org/
next prev parent reply other threads:[~2003-07-25 1:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-25 0:56 why the current kernel config menu layout is a mess Robert P. J. Day
2003-07-25 1:27 ` Bernd Eckenfels [this message]
2003-07-25 12:46 ` Robert P. J. Day
2003-07-25 14:10 ` Tomas Szepe
2003-07-25 13:18 Frederick, Fabian
2003-07-25 14:58 John Bradford
2003-07-25 15:07 ` Roman Zippel
2003-07-25 15:26 ` Robert P. J. Day
2003-07-25 15:51 ` Tomas Szepe
2003-07-25 16:11 ` Herbert Pötzl
2003-07-25 15:28 John Bradford
2003-07-25 15:53 John Bradford
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 \
* 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).