From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Rob Landley <rob@landley.net>
Cc: dougg@torque.net, James Bottomley <James.Bottomley@steeleye.com>,
linux-scsi@vger.kernel.org
Subject: Re: Some quick scsi documentation questions:
Date: Mon, 06 Aug 2007 20:30:15 +0200 [thread overview]
Message-ID: <46B768B7.7000803@s5r6.in-berlin.de> (raw)
In-Reply-To: <200708061129.31012.rob@landley.net>
Rob Landley wrote:
> On Sunday 05 August 2007 11:50:33 am Douglas Gilbert wrote:
>> Stefan Richter wrote:
>>> Rob Landley wrote:
>>>> There are such things as external SATA enclosures, but
>>>> they're A) few and far between,
>>> What? They are all the rage now. :-)
...
> My point is that there are something like ten million of laptops produced
> annually and with enclosures you're talking about a technology where the
> entire production run generally doesn't hit six figures in unit volume. That
> would be "few and far between" in my book. (Don't get me started on cell
> phones. :)
The case of a laptop with a single sealed "spindle" (and maybe an
optical drive) is easy. Among else, you have the following options:
- Let the distributor figure it out for you.
- Link the driver for the onboard SATA controller statically into
the kernel. Make all other SCSI low-level providers (e.g. usb-
storage) modular.
In other words, if SATA and USB and other disks are mixed up, let the
distributor deal with the mix-up. You only ever deal with device
aliases in /dev/disk/by-*/ or with an even higher-level representation
by the desktop environment. _Or_ you enforce that the built-in SATA
drive is always /dev/sda, by having this drive always added first.
...
> Right now "this is a SATA drive" isn't exposed in sysfs, that I can find.
Have a look at the udev scripts or at Doug's lsscsi. Or simply use
lsscsi like a blackbox.
--
Stefan Richter
-=====-=-=== =--- --==-
http://arcgraph.de/sr/
next prev parent reply other threads:[~2007-08-06 18:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200707252328.28981.rob@landley.net>
[not found] ` <1185455711.3501.46.camel@localhost.localdomain>
2007-07-27 21:29 ` Some quick scsi documentation questions: Rob Landley
2007-08-02 18:41 ` Douglas Gilbert
2007-08-02 21:19 ` Stefan Richter
2007-08-03 0:55 ` Rob Landley
2007-08-03 10:43 ` Stefan Richter
2007-08-03 21:11 ` Rob Landley
2007-08-04 0:08 ` Stefan Richter
2007-08-04 0:35 ` Stefan Richter
2007-08-05 16:50 ` Douglas Gilbert
2007-08-06 16:29 ` Rob Landley
2007-08-06 18:30 ` Stefan Richter [this message]
2007-08-02 21:39 ` Stefan Richter
2007-08-03 1:12 ` Rob Landley
2007-08-03 8:15 ` Stefan Richter
2007-08-03 19:07 ` Rob Landley
2007-08-03 19:37 ` Stefan Richter
2007-08-03 21:39 ` Rob Landley
2007-08-03 0:39 ` Rob Landley
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=46B768B7.7000803@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=James.Bottomley@steeleye.com \
--cc=dougg@torque.net \
--cc=linux-scsi@vger.kernel.org \
--cc=rob@landley.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