Maybe configd not picking up on this is a bug so I'll file a bug
report and see what happens
Or maybe the fact that the MacBook Air needs to be able to netboot
wirelessly means that the AirPort driver suddenly needed to start
loading way before any of that fun SCF stuff becomes available to it.
The Leopard boot cycle hasn't been very well documented, so I have no
idea if that's true, but it wouldn't surprise me if it were a very
special driver with very special needs that were addressed on a very
tight deadline.
I think what you're doing now is the best possible solution all around.
