Re: IDE/ATAPI in 2.5

[Benjamin Herrenschmidt <benh@kernel.crashing.org>]

>
>How is it attached? Using FACL or ISCSI?
>
>In any case, it seems to be a natural solution to do it this way.
>
>In order to access a network disk, you need to obtain the right to
>do so first. Once this has been done, the netork subsystem just looks
>like a new SCSI bus.

The naming is nothing we should matter with. Ask Greg KH what he
thinks about kernel enforcing a naming policy ;)

What we are going to with 2.5 is a fully userland naming policy.

So if we end up defining a uniform API to send packet commands to
those type of devices (wether they are on a SCSI bus, ATAPI, USB,
1394, ...), then the best approach is probably for the various
drivers involved to declare a class "SCSI packet" in driverfs,
then let whatever userland naming policy decide how that should
be called. The internal kernel infrastructure (wether it'sa common
driver or split drivers providing you the same interface) is of
no matter to cdrecord.

Ben.