From: Jon Watte <jwatte@gmail.com>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: Andi Kleen <andi@firstfloor.org>,
James Bottomley <James.Bottomley@HansenPartnership.com>,
linux-scsi@vger.kernel.org
Subject: Re: AHCI finds disks; no /dev/sd inodes bound?
Date: Wed, 09 Jan 2008 12:36:26 -0800 [thread overview]
Message-ID: <4785304A.60109@gmail.com> (raw)
In-Reply-To: <4785138A.4000809@s5r6.in-berlin.de>
Stefan Richter wrote:
>> Those systems (servers) typically have enough memory to tolerate a few
>> extra KB of code without problems. In fact most PCs these days have.
>>
>
> It would be a stupid solution nevertheless.
>
> (We also don't "select EXT3".)
>
It's not the prettiest solution, but it would reduce the number of
"support incidents." And, after all, reducing the number of support
incidents is the goal of usability.
Not selecting EXT3 is a little more understandable, because there are
many options -- cramfs, xfs, reiserfs, etc, depending on target.
However, the number of people who DO want SATA support but DO NOT want
SD block device support is... uh.. anyone?
Solving the problem bigger and better, by factoring "SD" into a
mid-level menu, and maybe calling it something non-SCSI, would probably
be even better. And even more work.
OK, I'll go hide now and try not to fan any flames. And thanks again to
Andi for nailing my problem right away!
Cheers,
/ h+
next prev parent reply other threads:[~2008-01-09 20:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-09 7:40 AHCI finds disks; no /dev/sd inodes bound? Jon Watte
2008-01-09 16:45 ` Andi Kleen
2008-01-09 17:21 ` Jon Watte
2008-01-09 17:29 ` James Bottomley
2008-01-09 17:49 ` Andi Kleen
2008-01-09 18:33 ` Stefan Richter
2008-01-09 18:37 ` Stefan Richter
2008-01-09 18:50 ` Stefan Richter
2008-01-09 20:36 ` Jon Watte [this message]
2008-01-09 20:58 ` Matthew Wilcox
2008-01-09 21:41 ` Stefan Richter
2008-01-09 22:23 ` Andi Kleen
2008-01-09 23:03 ` Stefan Richter
2008-01-09 23:16 ` Stefan Richter
2008-01-10 0:38 ` Andi Kleen
2008-01-10 0:53 ` Stefan Richter
2008-01-10 4:47 ` Jeff Garzik
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=4785304A.60109@gmail.com \
--to=jwatte@gmail.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=andi@firstfloor.org \
--cc=linux-scsi@vger.kernel.org \
--cc=stefanr@s5r6.in-berlin.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.