-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 6/27/06, Denny White <[EMAIL PROTECTED]> wrote:
[snip]
okay while in xwindows from xterm. But, when I try to ssh
in from either obsd box to the windows box from a regular
terminal window, I get in, but after that, the screen is
blank. Only way to get the terminal window back is to exit
[snip]
am coming up blank. Just trying to find out if anyone else
has encountered this problem & what they did to solve it.
Today Jeff Quast wrote:
I have this problem with a freebsd shell provider.
I fixed it intermidently by starting screen before sshing out.
This filters out the garbage they output to my display.
Explicitly exporting TERM as vt220 or wsvt25 before you
ssh to the box may help as well. It didn't for me.
My best guess is the cgywin box has one of those
super-cool-eleet colored bash prompts.
touch ~/.hushlogin and set PS1=$ in the winbox .profile.
Setting PS1=$ and .hushlogin did not work for me, I requested
the shell provider to add an if statement in the global
profile to honor .hushlogin before printing out the stupid ansi colored
news/motd/whatever it was they were doing.
Had another box running FreeBSD 5.4 with identical ttys set
up and was able to login to the windows box from a terminal
window okay. Thanks for any help.
As Stuart pointed out, the term code is different.
Denny White
jdq
Thanks Jeff, and to Stuart also. Changed the bash shell prompt
to the same on these 2 obsd boxes & problem was solved. I'll
miss the color when working on the winxp box in cygwin, due
to my bad eyes, but I'll learn to live with it. :-) Thanks,
also, for the info about the differences in the term codes
between fbsd & obsd. 'Nother thing to read up on.
Denny White
GnuPG key : 0x1644E79A | http://wwwkeys.nl.pgp.net
Fingerprint: D0A9 AD44 1F10 E09E 0E67 EC25 CB44 F2E5 1644 E79A
iD8DBQFEoWXmy0Ty5RZE55oRAsajAKCUKNweUSuW/GAYwGsVfjaeNBrk5QCeKdoV
B+waI2HWSQhwaY/FkCVhaLY=
=H8hK
-----END PGP SIGNATURE-----
