Re: Telnet from Linux to SCO OpenServer 5.0.6
From: Brian K. White (brian_at_aljex.com)
Date: 04/29/03
- Next message: Roberto Zini: "Adaptec RAID 2110S on SCO OS 5.0.7"
- Previous message: Ian Wilson: "Re: Telnet from Linux to SCO OpenServer 5.0.6"
- In reply to: pierreforget: "Re: Telnet from Linux to SCO OpenServer 5.0.6"
- Next in thread: pierreforget: "Re: Telnet from Linux to SCO OpenServer 5.0.6"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: 29 Apr 2003 02:53:58 -0700
pierreforget <member28669@dbforums.com> wrote in message news:<2817234.1051565197@dbforums.com>...
> Hi,
>
> I tried echo -e "\033(U" from the Linux box and I get a blank line.
It changes the behaviour of the linux console in much the same way
"mapchan -n" does on sco. It doesn't do anything immediately
noticeable.
>
> If I check mapchan on the server, all the channels give a response of
> "NULL". I checked the default mapchan file and everything is set to
> "NULL". Meaning they are not using any mapchan. If I manually make a
> mapchan like this:
>
> mapchan /etc/default/ibm ttyp6
>
> I should theorically get the mapping I need.
>
> Am I right?
nope :)
the default mapchan file only lists console tty's by default, not any
of the tty's you get when you telnet in. so when you telnet in,
mapchan is usually in effect. you can add them but I don't recommend
doing it that way. the propper channel mapping cannot really be
determined by tty for network based logins because a particulatr tty
does not correspond to any particular peice of hardware the way it
does for (some) serial and the consoles. even in the case of serial
ttys the model is no good because a modem sits on a serial tty and any
kind of terminal could dial up the modem.
first just do like I suggested,
run the echo command on linux, telnet in to sco, run the mapchan
command on sco, then try the app, then relay the following info here
from that same session (so far these things will only affect a single
session)
echo $TERM
describe the character that is displayed where there is supposed to be
a top-left-corner, bottom-right-corner, any other line/box characters
you could describe. capital A with two dots, or just "q", etc...
from linux, are you telnetting from a text console oran xterm?
if an xterm, which one specifically? (kvt/gnome-term/e-term/rxvt/plian
old xterm/etc...) if it's from an xterm, then $TERM should not be set
to "linux" but "xterm" or "xterm-color" or "rxvt" (start with "xterm"
as it's the most likely to already exist in some form in your
applications proprietary termcap or terminfo, if it has one.
assuming you are telnetting right from the text console...
the echo command will tell the linux console not to remap the vga
hardware font. when the sco box application sends ascii character
octal 332, you should see a top-left-corner.
the mapchan -n command on sco will tell sco to send octal 332 when the
application tries to send octal 332 instead of trying to figure out
what character 332 is and send some other ascii value in it's place.
together, these form a sort of "clean" channel from your app to your
screen. that is, two things along the way have been told to keep their
hands off the data and simply send it along without futzing with it.
this may cause the application to start looking right all by itself,
but even if the application still looks wrong, at least now we will
know what characters the application is sending, and we can figure out
the best fix based on that.
a simple test at this point would be to run on the sco box:
echo "this is a top-left-corner: \0332"
if it looked right, then proceed to try the app.
if the application looks good at this point, then we can decide the
best way to make this fix permanent. more on that below...
> Now, if I want to keep this permanent only for this Linux station, how
> can I do this? All the stations or terminals get on with the same login,
> so if I modify the login, they other ones will be screwed up, if I
> understand right.
>
> All these machines or terminals have a fixed IP address. Will the same
> machine always logon to the same ttyp?
no
oh there are hacks that can be employed to force an app to start on a
particular tty or to cause your session to jump to a particular tty
but it's counter-productive to try and do that unless there is some
exotic need, which in this case there is not.
> Unless I create another login specifically for this Linux machine? Which
> would include the reference to the right mapchan?
no, there are various simple tricks that can be placed in /etc/profile
that will be run by everyone at login, detect the linux terminal and
perform commands only for the linux terminal, the simplest is
probably:
case $TERM in
linux)
mapchan -n
stty intr "^c"
stty erase "^?"
#tput smpch
# or
#tput smacs
# or
#echo "\033[11m"
# or
echo "\033(U"
;;
esac
the tput commands and the echo \033[11m command are just other
possible ways to do the same thing as the echo \033(U _if_ you have
the linux terminfo installed on the sco box and if that terminfo has
the smpch (set mode pc character set) or the smacs (set mode alternate
character set) neither of which is really the same as the \033(U which
says "don't even pretend to know anything about character sets just
ferry the ascii values along without touching them and let the
hardware display them however it will" but often do produce the
correct looking characters.
this block of stuff, pasted to the end of /etc/profile, will only do
anything if $TERM = "linux" during login, which will not be true for
the other terminals.
in the case of the linux box, it will do both the mapchan and the echo
\033(U and it will also correct a couple minor anoyances with respect
to the backspace and delete keys. it will not make the delete key work
like it does on the sco console or sco-ansi emulators, but it will
stop the backspace key from behaving like the delete key. it is
technically possible to make the delete key work like the sco console,
but it's such a pain in the neck that I am not even going to go into
it. the break key for linux and linux terminals is ctrl-c simple as
that.
- Next message: Roberto Zini: "Adaptec RAID 2110S on SCO OS 5.0.7"
- Previous message: Ian Wilson: "Re: Telnet from Linux to SCO OpenServer 5.0.6"
- In reply to: pierreforget: "Re: Telnet from Linux to SCO OpenServer 5.0.6"
- Next in thread: pierreforget: "Re: Telnet from Linux to SCO OpenServer 5.0.6"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
