On 03/12/06, Richard Troy <[EMAIL PROTECTED]> wrote:
On Sun, 3 Dec 2006, Paul Mason wrote: > > Are you using the console or an X-based xterm variant? > > If the former then vt100 should work. > > If the later then konsole and konsolel are in the latest versions. I > also wrote this document which is a step-by-step to creating one that > works with Linux X terminal programs - > http://docs.google.com/Doc.aspx?id=afzvthc6fzsm_afzv34f7znps ...I guess it got edited out during an earlier reply;
Actually I'm missing your original post - not sure why.
the database system has NO windowing GUI of any kind and is only accessible with SSH. I usually connect with a "console" terminal from the console of another system (also RH Linux) - I "ssh in" to the box. I've tried sshing in from a Windows system, too, using both cygwin bash and also F-Secure. All methods I've tried so far have the same flaws; no function keys other than the pf keys.
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) If you're connecting from Windows I'd recommend putty (http://www.chiark.greenend.org.uk/~sgtatham/putty/). Putty and vt100f works well.
Do you think your step-by-step will help me?
No it's only for X based terminal emulators.
...Somehow I just can't believe that there's no good solution "out of the box" - and if there isn't, then one needs to be added ASAP. This _is_ supposed to be an Open Source project, right?
On the one hand I think there is a solution "out of the box" in that it's pretty easy to find (and not too to hard to create) a termcap entry that'll work for whatever you're using. On the other hand we don't make it easy for you to find out how to do it. That's one reason I wrote that document. Whilst I'm not defending that I think I know why it happened. Back in the day, when Ingres forms system was written, people were using actual terminals and it wasn't that much to expect that people know what their actual hardware was and set an environment variable accordingly. Then later we had PCs and terminal emulators but most people still remembered enough to know what was going on. In any case it's on of those things you set up and then forget about. Then what started to happen was a focus on GUI tools. So we got Visual DBA and Visual Manager and so on. There was a general feeling that you didn't want someone's first experience to be character based tools. They looked and felt out of date. (Except to those of us happily using them but we were generally old hands who knew how to set up things.) So I think putting "how to set up TERM_INGRES" into the Getting Started Guide would have been not the done thing at that point. Then Linux started to become popular and a version of Ingres was released for it. Which worked fine if you connected using one of the terminal emulators that had always worked. If not then there were some instructions in the Release Notes, but not the GSG for reasons mentioned above. You see, up until that point the character based stuff hadn't changed for years - because no-one was logging on directly to unix hardware any more. Anyway - there are reasons why we got where we are today - not that that necessarily makes things any better. As for "it's an open source project right?" well that's a whole different discussion and one I'm not going to get into now. -- Paul Mason _______________________________________________ Users mailing list Users@lists.ingres.com http://lists.ingres.com/mailman/listinfo/users