D. Allen [CGL]" <idallen@watpix.waterloo.edu> (04/24/91)
Point some Ultrix /dev/ttyXX entry at a LAT port on your DECserver, e.g.
# lcp -h /dev/tty21:SERVER:PORT_1
then log in to the server (via ccr or another port), set priv mode,
enable remote modification on that PORT_1, and "MONITOR SESSIONS PORT 1".
Now run this Ultrix shell script to open that port and modify it:
#!/bin/sh
exec >/dev/tty21
stty
stty 2400 -raw
stty 2400 raw
stty
sleep 5
when the session first appears, you'll see that even though Ultrix thinks
the port is in "raw" mode, the DECserver claims "Interactive" mode for
the session. This is not what the DECserver should do. The DECserver
should set itself to match exactly the characteristicts of the Ultrix
port, and for "raw" mode that is "Passall" mode on the server.
You'd think that "stty raw" would fix the mode on the server, but it does
not. You have to first "stty -raw" and then "stty raw" to get the DECserver
to finally set "Passall" mode.
This might be a fault in the stty command, in the kernel, or in the
server. I believe it's in the kernel, since even if you use tip to
connect to the port, it gets opened in "Interactive" mode. Looks like
the kernel "knows" the Ultrix port is already in raw mode, so it doesn't
pass the "stty raw" information on to the DECserver so that it can
enter "Passall" mode. If you "stty -raw >/dev/tty21" before you use
tip, tip will correctly reset the port to "Passall" mode when it next
opens the port.
DECservers must set their ports to match what Ultrix thinks they are.
ULTRIX V4.1 (Rev. 52) DS5400
DECserver 200 Terminal Server V3.0 (BL33) - LAT V5.1
--
-IAN! (Ian! D. Allen) idallen@watcgl.uwaterloo.ca idallen@watcgl.waterloo.edu
[129.97.128.64] Computer Graphics Lab/University of Waterloo/Ontario/Canada