• Subject: Re: A couple of questions...
  • From: stevefx@xxxxxxxxxx
  • Date: Thu, 2 Dec 1999 15:00:43 -0600

Could someone please explain to me what this does? I thought it was just so
that you could get F21-F24 to work? The statement "so that I can use
xt5250" makes me wondering if I'm missing something here. I'm using
Mandrake 6.1 and xt5250 works just fine for me (with the exception of the
End and Field Exit keys...but I may have not set those up right???). I went
into the linux subdir and issued the 'tic' command but I didn't notice any
other files created. What is the "proper place"?  I saw something else
about setting the TERM variable from xterm to xterm-5250. What does this

The reason I ask is because I have a cow-orker running RH6.1 and xt5250
does weird things for him.

Sorry for all the questions and TIA for any answers...

Steve Fox
http://w3.rchland.ibm.com/~sjfox (IBM Intranet)
http://pcxtreme.org (Personal)
http://k-lug.com (Rochester Linux User Group)


> 3. I do not know how to setup terminfo/termcap. Can someone assist with
> this so that I can use xt5250?

To set up a terminfo entry, do the following as root:

tic 5250.terminfo

... that compiles the entry and puts it in the proper place.  To use the
termcap entry instead, append the 5250.termcap to the end of your
file.  The terminfo is recommended, as it supports more information and

| This is the LINUX5250 Mailing List!
| To submit a new message, send your mail to LINUX5250@midrange.com.
| To subscribe to this list send email to LINUX5250-SUB@midrange.com.
| To unsubscribe from this list send email to LINUX5250-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].