From: "Randy.Dunlap" <rdunlap@xenotime.net>
To: Nico Schottelius <nico-kernel@schottelius.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.13.2 - menuconfig: raid support wrong place?
Date: Mon, 3 Oct 2005 19:59:38 -0700 [thread overview]
Message-ID: <20051003195938.779fa982.rdunlap@xenotime.net> (raw)
In-Reply-To: <20051003083537.GB1746@schottelius.org>
On Mon, 3 Oct 2005 10:35:37 +0200 Nico Schottelius wrote:
> Hello!
>
> Is it wanted, that some hardware raids are listed below
> "Block devices" and not IDE or SCSI support?
>
> And will SATA devices in general stay below SCSI?
>
> Both things aren't really intuitive to find and I would expect
> the raid drivers below IDE or SCSI and I was searching for SATA
> not below SCSI some times.
Yeah, we sometimes tend to put drivers in a menu depending
on what technology or interfaces they use.
E.g., some RAID drivers are under Block Devices because they are
implemented as block devices.
That's probably not the best place for them from a user
perspective, but instead of putting them under IDE or SCSI
support, I would rather see them merged with the
Multi-device support menu (RAID and LVM), which appears
to be mostly for infrastructure, not for device drivers,
but there could be a separate section of it for device drivers
IMO.
SATA (currently) uses SCSI software interfaces, so it lives in the
SCSI menus. Yes, that might not make sense to some people.
Maybe a separate menu for SATA would make sense...
Want to propose some changes via patches? I have no idea how
well accepted they might be.
---
~Randy
You can't do anything without having to do something else first.
-- Belefant's Law
prev parent reply other threads:[~2005-10-04 2:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-03 8:35 Nico Schottelius
2005-10-04 2:59 ` Randy.Dunlap [this message]
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=20051003195938.779fa982.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=linux-kernel@vger.kernel.org \
--cc=nico-kernel@schottelius.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®