linaro-pkg team mailing list archive

[Mark Shuttleworth <927781@xxxxxxxxxxxxxxxxxx>]

Out of curiosity, is there any standard or convention for the vendor-
class-identifier which would let this approach work well out of the box?
Sure, it seems one can make it work manually if one happens to have a
useful vendor class identifies to work with, but there's nothing there
that could be standardised and Just Work, especially with transitions
like v8, HF etc.

Ideally, we'd want to be able to have PXE just work in our provisioning
service, and hard-coding, or hand-coding, or hand-hard-coding specific
mappins as per the example isn't a solution.

-- 
You received this bug notification because you are a member of Linaro
Maintainers, which is the registrant for Linaro U-Boot.
https://bugs.launchpad.net/bugs/927781

Title:
  PXELINUX implementation doesn't respect dhcp ConfigFile or PathPrefix
  values

Status in Linaro U-Boot:
  New
Status in “u-boot-linaro” package in Ubuntu:
  In Progress

Bug description:
  The part implementation of PXELINUX in uboot doesn't respect RFC5071 dhcp options:
     o  "MAGIC" - 208 - An option whose presence and content verifies to
        the PXELINUX bootloader that the options numbered 209-211 are for
        the purpose as described herein.

     o  "ConfigFile" - 209 - Configures the path/filename component of the
        configuration file's location, which this bootloader should use to
        configure itself.

     o  "PathPrefix" - 210 - Configures a value to be prepended to the
        ConfigFile to discern the directory location of the file.

     o  "RebootTime" - 211 - Configures a timeout after which the
        bootstrap program will reboot the system (most likely returning it
        to PXE).

  These have the obvious interest in being able to provide customised
  config and kernels at run time.

  Thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/u-boot-linaro/+bug/927781/+subscriptions