Re: [RFC] aic94xx: attaching to the sas transport class

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



--- Stefan Richter <stefanr@xxxxxxxxxxxxxxxxx> wrote:
> Same for SBP-2. This is old and has been solved before.
> 
> Neither attempts to enforce a specific order of device registering, nor
> a delay of an module init routine in order to wait for completion of
> device discovery is a proper solution. Let alone an empirically chosen
> delay.

BIOSes accomplish this task.

> Create an initrd. Put the necessary hotplug infrastructure into the
> initrd. This includes
>  - reacting on device hotplugs,
>  - mapping persistent unique device identifiers or unique partition
>    identifiers to mount points,
> i.e. basically everything which has to be done for hotpluggable devices.
> 
> (Put policy into userspace. Let the kernel provide mechanism only.)

Yes, this is a very good idea.

      Luben

-
: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [SCSI Target Devel]     [Linux SCSI Target Infrastructure]     [Kernel Newbies]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Linux IIO]     [Samba]     [Device Mapper]
  Powered by Linux