Jonathan Stone wrote:
> Not entirely. On some ports `installboot' is a no-op (since the
> secondary bootstrap isn't pinned); on other ports, installboot updates
> the primary. A restore (say), or an interrupted upgrade, or developer
> hacking, could leave a disk with both old, and new bootblocks (/boot
> and /boot.${MACHINE}).
> 
> Which one does the primary load?

The new /boot.${MACHINE} IMHO :) There is bigger chance new primary
will work correctly with new secondary then a chance new primary
would work with old secondary.

Jaromir