mirror of https://github.com/Qortal/Brooklyn
You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
33 lines
1.5 KiB
33 lines
1.5 KiB
What: /sys/firmware/ibft/initiator |
|
Date: November 2007 |
|
Contact: Konrad Rzeszutek <[email protected]> |
|
Description: The /sys/firmware/ibft/initiator directory will contain |
|
files that expose the iSCSI Boot Firmware Table initiator data. |
|
Usually this contains the Initiator name. |
|
|
|
What: /sys/firmware/ibft/targetX |
|
Date: November 2007 |
|
Contact: Konrad Rzeszutek <[email protected]> |
|
Description: The /sys/firmware/ibft/targetX directory will contain |
|
files that expose the iSCSI Boot Firmware Table target data. |
|
Usually this contains the target's IP address, boot LUN, |
|
target name, and what NIC it is associated with. It can also |
|
contain the CHAP name (and password), the reverse CHAP |
|
name (and password) |
|
|
|
What: /sys/firmware/ibft/ethernetX |
|
Date: November 2007 |
|
Contact: Konrad Rzeszutek <[email protected]> |
|
Description: The /sys/firmware/ibft/ethernetX directory will contain |
|
files that expose the iSCSI Boot Firmware Table NIC data. |
|
Usually this contains the IP address, MAC, and gateway of the NIC. |
|
|
|
What: /sys/firmware/ibft/acpi_header |
|
Date: March 2016 |
|
Contact: David Bond <[email protected]> |
|
Description: The /sys/firmware/ibft/acpi_header directory will contain files |
|
that expose the SIGNATURE, OEM_ID, and OEM_TABLE_ID fields of the |
|
acpi table header of the iBFT structure. This will allow for |
|
identification of the creator of the table which is useful in |
|
determining quirks associated with some adapters when used in |
|
hardware vs software iscsi initiator mode.
|
|
|