| All Forums |
Register |
Login |
Search |
Subscriptions |
My Profile |
Inbox |
| Tool Warehouse |
FAQs |
Resources |
Help |
Member List |
Address Book |
Logout |
|
|
TERM setting
|
Logged in as: Guest |
| Users viewing this topic: none |
|
Login  |
|
|
 TERM setting - Jan. 22, '04, 2:27:22 PM
|
|
|
Tim_Rogers
Posts: 7
Joined: Jan. 22, '04,
Status: offline
|
This is a basic question - but I cannot use SFU effectively until I resolve it!
I have downloaded and installed SFU 3.5, downloaded and installed SSH, and I can connect to my various Linux servers.
However, on connection, I get the following warning:
unknown terminal " interix"
Is there a way that I can add a definition for " interix" to the TERMCAP (I assume) for each Linux box? Even better, is there a way that I can change the TERM for the SFU shell?
|
|
|
|
|
RE: TERM setting - Jan. 22, '04, 3:03:58 PM
|
|
|
Woody2143
Posts: 3
Joined: Jan. 22, '04,
Status: offline
|
If you are using bash (and I suggest that you do) do this:
export TERM=" xterm" to change the term...
google can tell you how to set environment vars for korn or csh if you are going to use those....
|
|
|
|
|
RE: TERM setting - Jan. 22, '04, 3:18:40 PM
|
|
|
Tim_Rogers
Posts: 7
Joined: Jan. 22, '04,
Status: offline
|
Thanks for the quick reply.
I have installed ' bash' , and I did try several TERM settings, including ' xterm' .
Changing the TERM value, however, will prevent Linux from complaining about my terminal when I log in, but applications (e.g., emacs, mc) still do not work correctly - I suspect because the SFU shell is not, in fact, an XTERM!
Am I missing something?
|
|
|
|
|
RE: TERM setting - Jan. 22, '04, 5:34:14 PM
|
|
|
Woody2143
Posts: 3
Joined: Jan. 22, '04,
Status: offline
|
The only other thing I can think of off the top of my head is that the window you are using to log in is to big, I' ve had ' vi' complain to me before about the window size...
Post what error messages you are getting if any at all...
|
|
|
|
|
RE: TERM setting - Jan. 22, '04, 5:37:41 PM
|
|
|
Woody2143
Posts: 3
Joined: Jan. 22, '04,
Status: offline
|
Also take a look here:
|
|
|
|
|
RE: TERM setting - Jan. 22, '04, 9:03:37 PM
|
|
|
Tim_Rogers
Posts: 7
Joined: Jan. 22, '04,
Status: offline
|
No joy.
If I set the TERM value to ' xterm' and connect to one my my Linux boxes (Red Hat 7.3, mostly), then start emacs, I get some odd information in the status line (e.g., 25H25h and 25l[inverse video]7) and, replacing the information at the start of each line in the file, a 25h25h each time I press down error. At that point, I exit.
The remote bash shell itself is better - up error, for example, shows the previous value in history - and it may actually be fine. But without emacs and mc (sad, but true), I feel lost.
If I could run a remote X application, as I did when I was using Linux on my laptop, that would be fine - I could just use nedit or something. But that is a whole other thing.
And I am *not* going to learn vi!
|
|
|
|
|
RE: TERM setting - Jan. 24, '04, 2:45:10 AM
|
|
|
Rodney
Posts: 3696
Joined: Jul. 9, '02,
From: /Tools lab
Status: online
|
The default terminal is named " interix" .
When you make a connection to a remote machine (via telnet, ssh,...) the TERM env var for your local session is sent (" interix" ).
The " interix" terminal is an ANSI compliant terminal with extensions that are akin to vt202 (but not an exact match). Having " xterm" as the TERM env var won' t gain you anything. What you need to do on the remote machine is create an " interix" terminal entry with terminfo.
You can find the terminfo description in " /usr/share/terminfo.src" . Copy this over to the remote machine and get it added to the terminfo database (' man tic' for more info).
|
|
|
|
|
RE: TERM setting - Jan. 25, '04, 4:05:07 PM
|
|
|
markfunk
Posts: 669
Joined: Mar. 31, '03,
Status: offline
|
On the SFU/Interix system, type:
infocmp interix
Save the output and copy it to your remote UNIX/Linux system.
On your remote UNIX system, log in and read about the ' tic' utility. You may need to create your own personal terminfo directory and/or modify the TERMINFO env. variable appropriately so that terminfo/curses based programs on the remote system will work when connected via an Interix console window.
|
|
|
|
|
RE: TERM setting - Jan. 26, '04, 4:55:25 PM
|
|
|
Tim_Rogers
Posts: 7
Joined: Jan. 22, '04,
Status: offline
|
Thanks for the helpful replies - both of you!
I ' scp' ed the output of ' infocmp interix' to one of my Linux boxes, and, as root, used ' tic -v [filename]' to import it into the TERMINFO database.
Everything seems to work. (Yahoo!)
But - ' tic -cv [filename]' did show a warning:
[root@xserver-1 tmp]# tic -cv interix.txt
" interix.txt" , line 2, terminal ' interix' : Conflicting key definitions (using the last)
... KEY_END is the same as KEY_LL
... KEY_F(0) is the same as KEY_F(10)
Is this anything to worry about?
|
|
|
|
|
RE: TERM setting - Jan. 26, '04, 5:13:58 PM
|
|
|
Rodney
Posts: 3696
Joined: Jul. 9, '02,
From: /Tools lab
Status: online
|
No worries.
You' ll have a hard time finding a keyboard with an " F0" key.
|
|
|
|
|
RE: TERM setting - Jan. 26, '04, 5:22:30 PM
|
|
|
Tim_Rogers
Posts: 7
Joined: Jan. 22, '04,
Status: offline
|
Ha!
(Maybe I just actually read the error message! That is what I am always telling my users to do...)
Thanks.
|
|
|
|
|
RE: TERM setting - Feb. 19, '04, 6:06:16 AM
|
|
|
Johan Davidsson
Posts: 1
Joined: Feb. 19, '04,
Status: offline
|
quote:
ORIGINAL: Rodney
The default terminal is named " interix" .
When you make a connection to a remote machine (via telnet, ssh,...) the TERM env var for your local session is sent (" interix" ).
The " interix" terminal is an ANSI compliant terminal with extensions that are akin to vt202 (but not an exact match). Having " xterm" as the TERM env var won' t gain you anything. What you need to do on the remote machine is create an " interix" terminal entry with terminfo.
You can find the terminfo description in " /usr/share/terminfo.src" . Copy this over to the remote machine and get it added to the terminfo database (' man tic' for more info).
You just cant go to every host in a production system and define a new terminal. This is extremely stupid of interix to invent their own standard.
I have tried to set the TERM to ansi which works well when I get to other machines, mainly Solaris and extreme switches but now vi fails on my own machine.
Any ideas.......
Best Regards Johan
_____________________________
Sauron recommends windows XP for his minions
|
|
|
|
|
RE: TERM setting - Oct. 21, '05, 3:08:07 PM
|
|
|
boydo
Posts: 6
Joined: Aug. 10, '04,
Status: offline
|
Any further suggestions on this subject? I also am in a situation where in the sarbanes-oxley world we can't just go in and make changes on production systems...
thx
bk
|
|
|
|
|
RE: TERM setting - Oct. 21, '05, 5:31:56 PM
|
|
|
Rodney
Posts: 3696
Joined: Jul. 9, '02,
From: /Tools lab
Status: online
|
There is a bunch of information on the manual page for tic.
You can add the interix terminal entry to your terminfo database if it is not already there.
The standard OSS based terminfo database has had an interix terminal entry for more than a few years.
The vendor should be encouraged to update.
You can, per user, set the environment variable TERMINFO to point at an alternate location for
the terminfo database (that's the whole database). In general, users don't have the ability to
modify entries in these locations.
For "average" users $HOME/.terminfo is a directory that each user has control over that new entries
can be added to. The order is TERMINFO, then $HOME/.terminfo and then the default location.
Since $HOME/.terminfo is a user setting, and not a system setting...
You may also use xterm or rxvt terminals -- in either direction.
Assuming you have an Xserver on the Windows machine you can either start an xterm
locally and then login to the remote machine, OR login to the remote machine and then
set DISPLAY back to the Windows machine before starting a xterm on the remote machine.
|
|
|
|
|
RE: TERM setting - Apr. 14, '06, 6:35:01 AM
|
|
|
Cthulhu
Posts: 17
Joined: Mar. 3, '04,
Status: offline
|
quote:
ORIGINAL: Tim_Rogers
Thanks for the helpful replies - both of you!
I ' scp' ed the output of ' infocmp interix' to one of my Linux boxes, and, as root, used ' tic -v [filename]' to import it into the TERMINFO database.
Everything seems to work. (Yahoo!)
hmmm... I made the same(not exactly - not scp but Ctrl-C/V) and I saw:
[root@localhost root]# mc
Your terminal lacks the ability to clear the screen or position the cursor.
[root@localhost root]#
I find some differences between output from 'infocmp interix' and interix entry in /usr/share/terminfo.src and try to compile from .src file. Now Midnight Commander run, but look like this:
Τφξ<ΤφΗ/ΤφΗΤφΗΤφΗΤφΗΤφΗΤφΗΤφΗΤφΗΤφΗΤφΗΤφΗΤφΗΤφΗΤφΗΤφΗΤφΗΤφΗΤφΗΤφΗΤφΗΤφΗΤφΗΤφΗΤφΗ
Τφι Nazwa ΤφιRozmiarΤφι CzasM ΤφιΤφι Nazwa ΤφιRozmiarΤφ
Τφι/bin Τφι 4096Τφι14 kwi 07:40ΤφιΤφι/.. ΤφιNADRZEDΤφ
Τφι/boot Τφι 1024Τφι13 kwi 1/.. ΤφιNADRZEDΤφι
/dev Τφι 118784Τφι13 kwi 1/.gconfd Τφι 4096Τφι12 kwi 15
:49/etc Τφι 4096Τφι14 kwi 0/.mc Τφι 4096Τφι14 kwi 11
:10/home Τφι 4096Τφι25 sty .Xresources Τφι 1126Τφι23 sie 1
995/initrd Τφι 4096Τφι25 sty .bash_history Τφι 514Τφι14 kwi 11
:41/lib Τφι 4096Τφι14 kwi 0 .bash_logout Τφι 24Τφι10 cze 2
000/lost+found Τφι 16384Τφι12 kwi 1 .bash_profile Τφι 234Τφι 5 lip 2
001/misc Τφι 4096Τφι28 sty .bashrc Τφι 176Τφι23 sie 1
995/mnt Τφι 4096Τφι13 kwi 0 .cshrc Τφι 210Τφι10 cze 2
000/opt Τφι 4096Τφι25 sty .tcshrc Τφι 196Τφι11 lip 2
000/proc Τφι 0Τφι13 kwi 1 anaconda-ks.cfg Τφι 916Τφι13 kwi 07
:11/root Τφι 4096Τφι14 kwi 1 apt-0.5.~386.rpmΤφι 877691Τφι14 kwi 06
:45/sbin Τφι 8192Τφι14 kwi 0 big-sist~pre.zipΤφι1347018Τφι14 kwi9:5
046/tftpboot Τφι 4096Τφι13 kwi 0 bigsiste~rch.rpmΤ104065332Τφι14 k9:506
:46/tmp Τφι 4096Τφι14 kwi 1 bigsiste~rch.rpmΤφ 240523Τφι14 kwi509
:10ΤφΗΤφΗΤφΗΤφΗΤφΗΤφΗΤφΗΤφΗΤφΗΤφΗΤφΗΤφΗΤφ bigsiste~rch.rpmΤφ 398711Τφι14 kwi509
:09/bin ΤφιΤφι/..
ΤφφΤφΗΤφΗΤφΗΤφΗΤφΗΤφΗΤφΗΤφΗΤφΗΤφΗΤφΗΤφΗΤφ/.. φΗΤφ
ΗΤφΗΤφΗΤφΗΤφΗΤφΗΤφΗΤφΗΤφΗΤφΗΤφΗΤφΗΤφΗΤφśΤφφΤφΗΤφΗΤφΗΤφΗΤφΗΤφΗΤφΗΤφΗΤφΗΤφΗΤφΗΤφΗΤ
φΗΤφΗΤφΗΤφΗΤφΗΤφΗΤφΗΤφΗΤφΗΤφΗΤφΗΤφΗΤφΗΤφΗΤφΗΤφΗΤφΗΤφΗΤφΗΤφΗΤφΗΤφΗΤφΗΤφΗΤφΗΤφΗ[^]
[root@localhost root]#. 4Edycja 5Skopiuj6Przen. 7Utw├│rz 8Usu┼δ 9Rozwi┼δ 10Ko┼
δcz
any ideas?...
regards
Cth.
|
|
|
|
|
RE: TERM setting - Apr. 14, '06, 7:14:15 AM
|
|
|
Rodney
Posts: 3696
Joined: Jul. 9, '02,
From: /Tools lab
Status: online
|
That's certainly different... I wonder if it is because of the locale?
That is, a different character set is being used that has the characters you
show above at the same numeric location as the graphic characters with other
character sets (notably English)?
|
|
|
|
|
RE: TERM setting - Apr. 14, '06, 7:34:57 AM
|
|
|
Cthulhu
Posts: 17
Joined: Mar. 3, '04,
Status: offline
|
Maybe - I'm using polish Windows, and english linux with polish settings (but probably with ISO-8859-2).
thanks.
Cth.
|
|
|
|
|
RE: TERM setting - Apr. 18, '06, 10:35:44 AM
|
|
|
woehlkmp
Posts: 102
Status: offline
|
quote:
You just cant go to every host in a production system and define a new terminal. This is extremely stupid of interix to invent their own standard.
...and Linux did this as well (there are plenty of systems around my office that don't know what 'TERM=linux' means!). I went with Rodney's suggestion, except a little more so; I built a full, modern terminfo database from the ncurses source, dropped the whole thing in ~/.terminfo, and set TERMINFO to point to it. Problem solved.
Were you still having trouble with keys not doing what they're supposed to, or is that working?
|
|
|
|
|
RE: TERM setting - Apr. 23, '06, 12:29:49 PM
|
|
|
ender
Posts: 13
Joined: Aug. 16, '05,
Status: offline
|
Cthulhu: check if your locale uses UTF8 - that mc definitely looks like it's trying to use that.
|
|
|
|
 New Messages |
 No New Messages |
 Hot Topic w/ New Messages |
 Hot Topic w/o New Messages |
|
 Locked w/ New Messages |
 Locked w/o New Messages |
|
 Post New Thread
Reply to Message
Post New Poll
Submit Vote
Delete My Own Post
Delete My Own Thread
Rate Posts |
|
|
|
Printable Version
