This problem appears to be traceable to an old aboot boot image, and has been corrected as described in bug 480014. Please close this report and refer it to that one. Thanks, -Scott