Post Reply 
 
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
iPXE, iSCSI and int13
2016-03-07, 23:44
Post: #2
RE: iPXE, iSCSI and int13
(2016-03-07 00:55)mr_jrt Wrote:  Just wondering...this is all very new to me, but do iPXE's int13 hooks mean that you would expect the sanhook'ed iSCSI target to show up as a browsable (hdx) device in GRUB4DOS (command line, (hd<tab to auto complete>), or indeed, any code that utilises int13?

The iPXE SAN disk will be visible to anything that was started from within iPXE.

If you allow iPXE to exit, then the SAN drive will (usually) be unhooked.

Michael
Visit this user's website Find all posts by this user
Quote this message in a reply
Post Reply 


Messages In This Thread
iPXE, iSCSI and int13 - mr_jrt - 2016-03-07, 00:55
RE: iPXE, iSCSI and int13 - mcb30 - 2016-03-07 23:44
RE: iPXE, iSCSI and int13 - mr_jrt - 2016-03-07, 23:53
RE: iPXE, iSCSI and int13 - mr_jrt - 2016-03-09, 00:48
RE: iPXE, iSCSI and int13 - mr_jrt - 2016-03-10, 01:58
RE: iPXE, iSCSI and int13 - NiKiZe - 2016-03-10, 19:34
RE: iPXE, iSCSI and int13 - mr_jrt - 2016-03-11, 02:14
RE: iPXE, iSCSI and int13 - mr_jrt - 2016-03-12, 00:21
RE: iPXE, iSCSI and int13 - mcb30 - 2016-03-12, 03:17
RE: iPXE, iSCSI and int13 - mr_jrt - 2016-03-12, 13:32
RE: iPXE, iSCSI and int13 - mcb30 - 2016-03-12, 14:02
RE: iPXE, iSCSI and int13 - mr_jrt - 2016-03-12, 15:47



User(s) browsing this thread: 1 Guest(s)