summaryrefslogtreecommitdiffstats
path: root/sys/boot/forth/menu-commands.4th
diff options
context:
space:
mode:
authoravg <avg@FreeBSD.org>2011-07-25 09:12:48 +0000
committeravg <avg@FreeBSD.org>2011-07-25 09:12:48 +0000
commit50b05401d3190631fb48430b4c0b48789f259b8d (patch)
treeff97ee9903ea140928fcd9303e0d93873d3c2d2e /sys/boot/forth/menu-commands.4th
parentffeefed9fc8fa85d3fcbd19640ba38e51e2ff4da (diff)
downloadFreeBSD-src-50b05401d3190631fb48430b4c0b48789f259b8d.zip
FreeBSD-src-50b05401d3190631fb48430b4c0b48789f259b8d.tar.gz
remove RESTARTABLE_PANICS option
This is done per request/suggestion from John Baldwin who introduced the option. Trying to resume normal system operation after a panic is very unpredictable and dangerous. It will become even more dangerous when we allow a thread in panic(9) to penetrate all lock contexts. I understand that the only purpose of this option was for testing scenarios potentially resulting in panic. Suggested by: jhb Reviewed by: attilio, jhb X-MFC-After: never Approved by: re (kib)
Diffstat (limited to 'sys/boot/forth/menu-commands.4th')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud