9A500n Update Weirdness?
Has anyone encountered any update weirdness on their Leopard seed update to 9A500n? Without getting specific (and I’m not asking you to either, btw) I encountered something quite out of the ordinary after installing the package from a routine update via Software Updater. This happened to me AFTER the update but before the restart… I suppose it’s off the the bug reporter with me. ACK!