OT: linux vs vt100 termcap problems + screen - help!

[Fairlight]

>From inside the gravity well of a singularity, Brian K. White shouted:
> I have not looked deeply into it since I haven't cared yet, but trying 
> to help someone else here the other day I saw that screen sets TERM to 
> "screen.${TERM}", and in /etc/termcap there are screen.linux, 
> screen.rxvt etc...

THANK YOU!

Setting local to linux and remote to screen.linux works perfectly for both
yast on Linux, and mutt on Solaris and Linux.

My only real annoyance is that I might log into the Solaris server either
directly from Anzio (or PuTTY), or I may log in from inside screen--both
from the same IP#--and they won't enable sshd environment setting for users
due to (valid) security concerns.  So I have yet to figure out an
-automated- way of making my login process decide if it should run linux or
screen.linux, since I'm coming from the same IP# no matter what (in this
case, anyway).  If anyone has a genius solution to that, let me know.  I've
been over things six ways from Sunday and can't figure out a decent way to
determine a decent way to automate setting TERM to the right one yet.

Other than that, the raw solution works.  Got it working with custom
TERMINFO and TERMCAP variables and files last night, and got the admin to
install screen.termcap into both termcap and terminfo today once I knew it
would work.

THANKS, Brian!  HUGE help!

Thanks to everyone that gave input...the effort is appreciated greatly!

mark->