[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20060809221857.GG3691@stusta.de>
Date: Thu, 10 Aug 2006 00:18:57 +0200
From: Adrian Bunk <bunk@...sta.de>
To: Alan Cox <alan@...rguk.ukuu.org.uk>
Cc: linux-kernel@...r.kernel.org, linux-ide@...r.kernel.org
Subject: Re: /dev/sd*
On Wed, Aug 09, 2006 at 11:01:43PM +0100, Alan Cox wrote:
> Ar Mer, 2006-08-09 am 23:21 +0200, ysgrifennodd Adrian Bunk:
> > It might be a bit out of the scope of this thread, but why do some many
> > subsystems use the /dev/sd* namespace?
> >
> > Real SCSI devices use it.
> > The USB mass storage driver uses it.
>
> USB storage is real SCSI.
Real SCSI for a developer, for a user it's USB.
And things become even more confusing considering that the drive might
show up as /dev/sda or /dev/uba depending on the driver used.
> > libata uses it.
> >
> > I'd expext SATA or PATA devices at /dev/hd* or perhaps at /dev/ata* -
> > but why are they at /dev/sd*?
>
> ATA uses the top half of the scsi stack so ends up using the top layer
> scsi drivers. Its probably more efficient than writing new driver
> clones, especially as non disk ATA is also real SCSI (or very close).
You are talking about kernel<->kernel and kernel<->hardware interfaces.
I'm more concerned about the kernel<->userspace interface.
> You can use /dev/ata if you want - its just a udev problem ;)
Or by adding some manual links if using a static /dev.
But I'm still not getting the point why the /dev/sd* namespace has to be
used.
> Alan
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists