The headless systems, or boxes that may be far away are a pain to get back online if stuck during the boot sequence... (embedded/headless do not have IP-KVM or remote control). * The point is : with a headless system you want it back online, really. Even if it needs maintenance, you need a ssh or whatever to get your hands dirty. So don't stop the boot sequence. If it's damaged beyond basic/rescue usability, it makes no difference anyway.
JMNSHO:It is certainly much better to have the predictable known behavior of "no machine" than to have a machine whose behaviour is unkown and unknowable.
------------------------------------------------------------------------- | Paul Goyette | PGP Key fingerprint: | E-mail addresses: | | Customer Service | FA29 0E3B 35AF E8AE 6651 | paul at whooppee.com | | Network Engineer | 0786 F758 55DE 53BA 7731 | pgoyette at juniper.net | | Kernel Developer | | pgoyette at netbsd.org | -------------------------------------------------------------------------