early x86 microcode loading

[Simon J. Gerraty]

Eric van Gyzen <eric at vangyzen.net> wrote:
> I hesitate to suggest this, due to the necessary change in /two/ boot
> loaders, but...  The foo.d approach is very convenient for packages.  An
> activation script installed by the port/package could create a new
> /boot/loader.conf.d/devcpu-data file containing these lines.  A
> pkg-message would instruct the user to run it.

The ability for packages to add to the boot env is indeed nice,
(we do that in Junos) but a loader.conf.d/ would be problematic for
anyone whating verification (at least using my implementation) during
boot.

Allowing subdirs such that a loader.conf snippet, the module (or
whatever) and associated signatures could all co-exist without
interference with other packages works nicely.