On Thu, 22 Apr 1999, Michael J. Tuciarone wrote:
Do you mean, "type <break> on the console and drop to the ok prompt just like on a Sun workstation?"
I do, exactly!
If so, we consciously decided *not* to implement that behavior because such innocuous activites as plugging and unplugging the console cable could drop you into firmware.
Only if you have a really DUMB terminal (pun intended), or an administrator with similar qualities for that matter. BTW, unplugging the terminal does not have that effect, and only some terminals are stupid enough to "send a break" when you turn them on (assert CD or something, I forget). I don't have a problem with providing an environment variable to enable this just as in "boot-floppy," but I have to tell you that this is for me THE MOST ANNOYING "FEATURE" of the NAC. I think that there are plenty of NAC admins that hate being patronized by vendors in this way.
This is the only thing that makes me go down to the computer room in order to fix a NAC that had a bad day aside from changing hardware and VERY BAD things when OpenBoot hangs (hasn't happened yet on a NAC <knock on wood>).
Given a choice, we chose to try and keep the server up, no matter what.
Not the best idea considering that trying to reboot your server with corrupted disks puts it into a "neverending" loop.
Also, the equivalent of the "go" command would be very usefull to go along with the above.
Have you tried "go"? :-)
I think I did, although I'm not sure how usefull it is considering that there is no breaking on the console. I do have a box that's not in service yet, I'll verify if "go" exists. If it does, all I need is a super secret way of dropping the box to the ok prompt from the console. ;) Pleeeeeeeeaaaaaaaaaase! ;)
Tom