| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-Id: <20070926141335.8faa5cb9.randy.dunlap@oracle.com> Date: Wed, 26 Sep 2007 14:13:35 -0700 From: Randy Dunlap <randy.dunlap@...cle.com> To: Konrad Rzeszutek <konrad@...nok.org> Cc: linux-kernel@...r.kernel.org, pjones@...hat.com, konradr@...hat.com, konradr@...ux.vnet.ibm.com Subject: Re: [PATCH] Add iSCSI iBFT support. On Wed, 26 Sep 2007 14:46:52 -0400 Konrad Rzeszutek wrote: > This patch adds a /sysfs/firmware/ibft/table binary blob which exports > the iSCSI Boot Firmware Table (iBFT) structure. > > What is iSCSI Boot Firmware Table? i.e., what is this binary blob (?) I don't see a binary blob in this patch (as stated in the first sentence). I'd say that this patch adds methods for exporting (or exposing) the ibft thru sysfs. Is there some good reason that the iSCSI connection information shouldn't be exposed in real sysfs attribute files instead of just in a binary file? > It is a mechanism for the iSCSI > tools to extract from the machine NICs the iSCSI connection information > so that they can automagically mount the iSCSI share/target. Currently > the iSCSI information is hard-coded in the initrd. > > The full details of the structure are located at: > ftp://ftp.software.ibm.com/systems/support/system_x_pdf/ibm_iscsi_boot_firmware_table_v1.02.pdf --- ~Randy Phaedrus says that Quality is about caring. - 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