PXE Dispatcher for iPXE

[mcb30]

(2011-04-05 22:51)robinsmidsrod Wrote:  This behaviour does seem a bit counter-intuitive. I'm not entirely sure what would be the best behaviour, but failure to actually connect to the SAN URL and failure to actually boot the SAN drive (e.g. missing boot sector) could be considered different.
Failing to connect to the iSCSI target would for me indicate a hard fail, and should throw an exception, but failure to boot the drive is a sort of soft fail, because the problem is with the contents of the drive, and not in communicating with it. I would consider the last one a case of success (in a way).

For the sake of backwards compatibility, the sanboot command will have to fail for either reason. As mentioned elsewhere, I'm looking at implementing separate hook/unhook commands, which would allow you to do something like

Code:

sanhook ${root-path} || goto cannot_connect_to_target
sanboot || goto cannot_boot_from_target
sanunhook

Syntax may change before implementation.