I just wish there was a way to enable breaks from console.
By "enable breaks" do you mean the "BREAK causes the OS to jump to the PROM monitor" stuff that SunOS (including 5.x) does?
We don't detect BREAK or respond to it, but there's probably no reason we couldn't do that.
ARGGG! NO! NO! NO! Disaster waiting to happen. A failed terminal, or one that is turned off or has its power line unplugged generates a BREAK -well strictly speaking it's not really a BREAK but most implimentations of UART see it as a break. This used to happen to our Admin folks every once in a while with their SUN. Remember the users with their torches and pitchforks.
I don't know if our serial port is set up so that unplugging a terminal (or terminal server) and plugging it back in looks like a BREAK; that's one of the suckages on at least some Suns.
----- Stephen C. Woods; UCLA SEASnet; 2567 Boelter hall; LA CA 90095; (310)-825-8614 Finger for public key scw@cirrus.seas.ucla.edu,Internet mail:scw@SEAS.UCLA.EDU
On Fri, 23 Apr 1999 scw@seas.ucla.edu wrote:
ARGGG! NO! NO! NO! Disaster waiting to happen. A failed terminal, or one that is turned off or has its power line unplugged generates a BREAK -well strictly speaking it's not really a BREAK but most implimentations of UART see it as a break. This used to happen to our Admin folks every once in a while with their SUN. Remember the users with their torches and pitchforks.
I think you need some valium to calm down your paranoia.
We have 800 Suns, all of which have that feature. I haven't heard of any such uprising happening any time during a LONG history of this organization (pre Sun). This is especially hard to do with remote terminal servers. I think whether you want this or not should be toggled by and OpenBoot variable set to disabled by default.
I've made the mistake of turning on the terminal after it was plugged in to the Sun and halting it several times in my life. Every time I was able to type in "go" and the box continued to happily chug along. If you're giving console access to people that can't perform this simple step you shouldn't be an administrator.<- period
Tom
"tkaczma" == tkaczma tkaczma@gryf.net writes:
On Fri, 23 Apr 1999 scw@seas.ucla.edu wrote: ARGGG! NO! NO! NO! Disaster waiting to happen. A failed terminal, or one that is turned off or has its power line unplugged generates a BREAK -well strictly speaking it's not really a BREAK but most implimentations of UART see it as a break. This used to happen to our Admin folks every once in a while with their SUN. Remember the users with their torches and pitchforks.
tkaczma> We have 800 Suns, all of which have that feature. I haven't tkaczma> heard of any such uprising happening any time during a LONG tkaczma> history of this organization (pre Sun). This is especially tkaczma> hard to do with remote terminal servers. I think whether you tkaczma> want this or not should be toggled by and OpenBoot variable tkaczma> set to disabled by default.
I wish Sun would implement that. I've got a bunch of sun's on a terminal server and have never had a problem unless the cisco is powered off. That's acceptable; all the sysadmins know it, and no one else is allowed in the machine room (*cough*). Had a similar situation when I worked for an ISP.
Not once did you have any spurious breaks.
Now, if the NetApp wasn't able to immediately able to return to its previous running state after a "go", that would be a problem...
K.
In previous mail, Kendall Libby sez...
I wish Sun would implement that. I've got a bunch of sun's on a terminal server and have never had a problem unless the cisco is powered off. That's acceptable; all the sysadmins know it, and no one else is allowed in the machine room (*cough*). Had a similar situation when I worked for an ISP.
Err, I believe they did, a long while back; from an 'eeprom' dump:
ttyb-rts-dtr-off=false ttyb-ignore-cd=true ttya-rts-dtr-off=false ttya-ignore-cd=true ttyb-mode=9600,8,n,1,- ttya-mode=9600,8,n,1,-
these are the setting we use for this machine when connected to a Telebit NetBlazer serial brick for remote administration. These settings work fine, from an old sparc2 running 2.5.1.
John R. Dennison Senior Systems Administrator & Security Administrator WorldWide Access/Verio Chicago
On Fri, 23 Apr 1999, Kendall Libby wrote:
I wish Sun would implement that.
This could be desired in some environments.
I've got a bunch of sun's on a terminal server and have never had a problem unless the cisco is powered off. That's acceptable; all the sysadmins know it, and no one else is allowed in the machine room (*cough*). Had a similar situation when I worked for an ISP.
This is exactly the environment I have.
Not once did you have any spurious breaks.
Exactly!
Now, if the NetApp wasn't able to immediately able to return to its previous running state after a "go", that would be a problem...
Yes, but I don't anticipate many accidental "breaks," and rebooting the netapp after such incident is a non-event. It takes a couple minutes and it recovers itself beautifully BY DESIGN.
Tom
-
fubar＠mathworks.com -
John R. Dennison -
scw＠seas.ucla.edu -
tkaczma＠gryf.net