...

The "ipxe" directory under "boot" contains a file for every machine that boots buildroot.  The filename indicates the machine name.  In that file you will find a line like this:

...

Note that the BusyBox config file is reset every time a "make clean" is performed in buildroot (tool).  The other config files are preserved.  I plan to fix this.

Setting up

I first tried to unzip buildroot (tool) in AFS.  I much later hit a permissions issue during the build phase.  I would avoid AFS or any mounted file system.  I ultimately used aird-b50-srv01, under the /scratch directory.  In there I created a directory for my username (/scratch/egumtow).

Under that, you should have this structure:

• buildroot
  • buildroot-<year>.<month>-<version>
    • buildroot-<year>.<month>-<version>-<architecture> (created by unzipping the downloaded buildroot, and renaming the resulting directory)
    • site-top
    • host
    • download

Yes, it's repetitive.  But we will have many buildroots, and different architectures for each buildroot.

Behind the buildroot-<year>.<month>-<version>-<architecture> directory, you must symlink "site" to "../site-top".

Now you must run a SLAC-specific script (br-installconf.sh) to apply things.

And now you can run "make".  It should succeed, and if so, you can find the artifacts in the output/images/ directory.

Here is the full sequence of commands: