From: Dana Lacoste <dana.lacoste@peregrine.com>
To: linux-kernel@vger.kernel.org
Cc: "'Alan Cox'" <alan@lxorguk.ukuu.org.uk>, roy@karlsbakk.net
Subject: RE: Mylex/Compaq RAID controller placement in config
Date: Tue, 6 Nov 2001 08:01:31 -0800 [thread overview]
Message-ID: <B51F07F0080AD511AC4A0002A52CAB445B2863@ottonexc1.ottawa.loran.com> (raw)
> Well we could simplify it further by putting all
> configuration options under a single menu called
> "things". The controllers under block dont have
> drives appearing as /dev/sd*
I can understand the initial complaint, but I think it
comes down to a problem of user vs. developer :
For example : All of the SCSI devices are block devices,
aren't they? So how come they're not under "block devices"
in the menu?
All of the devices under "block devices" are storage controllers
(or ways of accessing storage in linux) so how come they're not
listed as such in the menuconfig options?
and then you hit the whole I20 problem. Half my raid controllers
aren't under either of those two menus.
Maybe ESR's config method would allow for a way of presenting the
menus in different ways? One for developers (who care more about
the subsystems and how they're connected) and one for users, who
care more about what the device does then how it's written?
--
Dana Lacoste Linux Developer
Peregrine Systems Ottawa, Canada
next reply other threads:[~2001-11-06 16:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-06 16:01 Dana Lacoste [this message]
2001-11-06 16:16 ` Alan Cox
2001-11-06 16:21 ` Richard B. Johnson
2001-11-06 16:44 ` Ricky Beam
-- strict thread matches above, loose matches on Subject: below --
2001-11-06 20:08 Stephen Cameron
2001-11-06 14:22 Roy Sigurd Karlsbakk
2001-11-06 15:15 ` Alan Cox
2001-11-06 15:15 ` Roy Sigurd Karlsbakk
2001-11-06 15:27 ` Arjan van de Ven
2001-11-06 15:35 ` Alan Cox
2001-11-06 16:00 ` Venkatesh Ramamurthy
2001-11-06 16:37 ` Ricky Beam
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=B51F07F0080AD511AC4A0002A52CAB445B2863@ottonexc1.ottawa.loran.com \
--to=dana.lacoste@peregrine.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=roy@karlsbakk.net \
/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®