While this may apply only to a very few people in rare circumstances, it is quite useful at those times. When a kernel panic occurs, the log information is stored in NVRAM for a reboot cycle, which means that if the information isn't saved after the first reboot, it's gone. For those like me who prefer to boot single-user to fsck manually after issues, and use reboot afteward, the panic information is lost. The way to save it is as follows:
- After fsck finishes with filesystem OK, mount / as writable:
% /sbin/mount -uw /
- Run panicdump to save the information:
% /usr/libexec/panicdump
- Finally, sync and reboot:
% sync;sync;sync;reboot
•
[9,722 views]

