[gPXE] [ipxe-devel] nomenclature to use...

[Shao Miller]

carlyoung at keycomm.co.uk wrote:
> *On Tue 09/11/10 1:40 PM , Shao Miller Shao.Miller at yrdsb.edu.on.ca sent:
> *
>
>     As a matter of fact, we do have a problem with such an odd
>     filename. You see, some HTTP URIs sometimes go something like
>     http://webserver/page#section and we do some processing with #.
>
>     While looking at this, I'd like to ask, though: Are you quite
>     certain that the DHCP + PXE service is configured correctly? Could
>     it be that #MPCPathBoot# is intended as a place-holder in the
>     CA-Unicenter Managed PC Boot Server settings? A palce-holder for
>     whatever the TFTP directory is supposed to be?
>
>     - Shao Miller
>
> Hi Shao,
> The #MPCPathBoot# prefix is a special path within the bootserver as 
> far as I am aware - sort of a virtual root I guess. It is a legal 
> file name on Windows and *NIX (though not a name I would use...)
> In my reading of this then, I should be asking HP to get this 
> addressed in the gPXE source code as it's not a bug in the TFTP 
> server, though I may be wise asking for an enhancement for that too to 
> use more "friendly" path names...?
> Many thanks for your assistance so far!

Yes.  HP might already have a new firmware image available for you to 
try, but I already see in the most recent source code that it's an 
issue, so I doubt it will resolve this.  It's worth approaching HP 
about, who will most likely then approach QLogic.

There were a few other changes to the Phantom driver (your NIC's driver) 
that Michael Brown has worked on, so the next time QLogic or HP provide 
a firmware image, you might find that it has iPXE included.

In the meanwhile, if anyone comes up with a change to the source code 
which resolves your issue, I'm not sure how you could flash it into the 
NIC, or if that'd void any warranty you might have, since it didn't come 
from HP.  However, if we can resolve your issue, you could build a CD or 
USB stick or even a floppy disk and change the boot order on the HP 
computer so that it boots such a device, rather than the NIC.  The 
device would then boot a version of iPXE/gPXE which could work for you.  
I only suggest that as an interim measure until HP could provide an update.

I hope this information is useful.

- Shao Miller
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://etherboot.org/pipermail/gpxe/attachments/20101109/aff240b8/attachment-0001.html