On 11/21/2014 06:43 AM, WANG Chao wrote: > Hi, > > On 11/20/14 at 03:56pm, Thomas Renninger wrote: >> From: Hannes Reinecke <h...@suse.de> >> >> Some iSCSI initiator present firmware information in >> /sys/firmware/ibft or /sys/firmware/iscsi_bootX >> >> Whenever we detect one of those directories we should assume >> that the iSCSI devices should be activated. >> >> Also incorporates SUSE patches: >> 0049: >> 95iscsi: Use 'ip=ibft' for ibft autoconfiguration >> >> For iBFT autoconfiguration we should be setting 'ip=ibft' >> instead of rd.neednet. This should instruct dracut to only >> enable the iBFT interfaces and leave the rest alone. > > I think, > > /sys/firmware/ibft is created for iBFT if detected. > /sys/firmware/iscsi_bootX is created for hardware iSCSI if detected. > Nope.
ibft is created whenever an iBFT section (either in system ROM or via EFI) is detected. iscsi_boot is created for be2iscsi devices, which use an iBFT-like interface. Both provide the same attributes. Cheers, Hannes -- Dr. Hannes Reinecke zSeries & Storage h...@suse.de +49 911 74053 688 SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg GF: J. Hawn, J. Guild, F. Imendörffer, HRB 21284 (AG Nürnberg) -- To unsubscribe from this list: send the line "unsubscribe initramfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
