On 04/12/06, Richard Troy <[EMAIL PROTECTED]> wrote:


On Mon, 4 Dec 2006, Paul Mason wrote:
> >
> > ...I guess it got edited out during an earlier reply;
>
> Actually I'm missing your original post - not sure why.
>

-shrug-


They did appear in my work account though - must check spam folder on gmail.

> Try TERM_INGRES=vt100fnl - I just tried that on Fedora Core 6 and it
> works fine. All the keys are from the keypad with PF1-PF4 being the
> top line (Numlock etc)

Just tried it; no luck. -big-frown- * and - on the keypad go to the top,
and not-quite-bottom, if that means anything...


Not really.

I can't imagine what's so unique about this setup. It's an older Red Hat
installation - no idea what, actually.  Probably 7.2 or some such.

7.2 is quite old. Try running uname -a and /lib/libc.so.6 to check the
versions of your kernel and libc. I don't think it would cause this
problem, and elsewhere you say stuff is working, but I'm not sure I'd
try to run Ingres 2006 on 7.2

...We're usually of the school; if it's not messed up, don't mess with it.
I was thinking perhaps it might be the character encoding. The term is
en_US.UTF-8. Perhaps you can tell me if that's what your system uses, too.


My work machine uses en_GB.UTF-8. The FC6 machine I tested on before
is my personal laptop which is at home so I can't check. However I
don't think the character encoding is relevant.

Did you mention what TERM setting you're using? Mine's set to "linux"
when I log on at the console.

You could go through and work out what your keys are generating and
write your own termcap entry - but that's rather tedious.

It might be worth eliminating the local machine. Can you log in
directly to the database server machine? If not, can you spare the
space on the local machine for an Ingres installation where you could
check if it behaves the same?

...Ya know, I just flashed on something; I recall that Linux (Red Hat at
least) is phaising out termcap, so I really noticed the termcap file
provided in the Ingres tree ($II_SYSTEM/ingres/files/termcap) and I'm
wondering if maybe I'm supposed to put this in some kind of path or
location in the system, etc. Hmmm... Ideas on that?  What is the file
provided in the Ingres distribution for? How is it pointed at so it's
used?

Ingres termcap is entirely separate to what Linux does. You don't need
to include your termcap on any Linux path. If you wanted to, you could
customize your termcap and use a different file and point to it using
II_TERMCAP_FILE but that's about where Ingres looks for the termcap
and doesn't relate to Linux.

Basically you set TERM_INGRES and Ingres uses that to look up your
terminal type in its own termcap file and acts accordingly.


Which brings up the question: What's Ingres got planned for the
elimination of termcap? (I think it's replaced by something like curses or
ncurses, or some such - don't know _anything_ about it except what I just
wrote.)

I don't think there's anything planned because we're not relying on
what Linux does. (I'm pretty sure Linux uses something else already -
terminfo?)


> If you're connecting from Windows I'd recommend putty
> (http://www.chiark.greenend.org.uk/~sgtatham/putty/). Putty and vt100f
> works well.

That was recommended. Haven't got it installed on my laptop at the moment,
but it's here somewhere. It's one of the free ssh packages our company
provides to employees so they can get access from home, etc. I'll try it
sometime soon. However, this isn't a great solution because it means I/we
have to always use a Windows box to get to Ingres and that just seems
particularly annoying.


You might want to look into using sql (line mode terminal monitor).
Also if you check the manual (Connectivity Guide) you'll see that
netutil has a non-interactive mode (i.e. doesn't use forms). Also
there's netu under the sig directory. You can edit config.dat directly
but then you lose and derived changes (some might say that's no bad
thing!).

--
Paul Mason
_______________________________________________
Users mailing list
[email protected]
http://lists.ingres.com/mailman/listinfo/users

Reply via email to