Then we tried the upgrade on another PM3. Oh shit! There is an RMA for it
now. Never had *this* happen before with a beta. Before ComOS was loaded
in completely it hanged for no apparent reason.
I tried doing a netboot and using the serial port to upload a new ComOS
with the brand spankin new Troubleshooting Guide instructions, but it gags
on tftp after about 42% or so, no matter which host platform/server
software is used for tftp (Win95 or UNIX). Tech support didn't know how the
download command worked, and the Troubleshooting Guide is horked on this
count (start the download before the PM3 is turned on? Huh?).
Tech support rep I talked to said it would be a "security problem" for them
to design it so that a jumper on the motherboard couldn't put the box back
in a sane state.
Say what?!
If I've got physical access to the box, I can remove the memory, unplug the
lines, stick a pencil in the fan, spit on the motherboard, spray paint
Ascend over the Livy logo....how is adding a jumper to get the box bootable
when it goes insane a security problem? That's what locks are for on the
rack.
Venting. But this is real life, not a cartoon. Whoever says this is a
security issue should have a little chat with me. Having written embedded
firmware for years I know this is not rocket science to provide a bootstrap
mechanism for restoring the OS.
Chris
-
To unsubscribe, email 'majordomo@livingston.com' with
'unsubscribe portmaster-users' in the body of the message.
Searchable list archive: <URL:http://www.livingston.com/Tech/archive/>