From: "\"Beerse, Corné\"" <c.beerse@torex-hiscom.nl>
To: "'Nahkola Mikko'" <mnahkola@trinms01.ntc.nokia.com>,
parisc-linux@lists.parisc-linux.org
Subject: RE: [parisc-linux] Terminfo/termcap for a 70096 ...
Date: Tue, 5 Aug 2003 15:04:24 +0200 [thread overview]
Message-ID: <03Aug5.152448cest.119163@ns.hiscom.nl> (raw)
[-- Attachment #1: Type: text/plain, Size: 2422 bytes --]
> -----Original Message-----
> From: Nahkola Mikko [mailto:mnahkola@trinms01.ntc.nokia.com]
>
> I tried to ask this question in the comp.sys.hp.hpux newsgroup once but
> didn't get any useful answers... anyone here know better?
The /etc/termcap file on a RedHat 7.3 machine does contain a bunch of HP
terminals, including 700 series like 700 44 and 700 92. I think the latter
one will suit your needs. There are even more. As far as I know, it all ends
in hpterm, the hp-terminal emulator (xterm equivalent) for X11 (vue) with
similar capabilities as the 700 series terminals.
Unfortunatly, while installing DebianWoody on a D370, I found none of them
in the terminfo database (and no termcap file). And the HP700/96 came with
the D370. I know one thing to do after finalizing the install....
>
> (yes, I know, this is probably specifically _not_ a problem on
> parisc-linux as all the parisc stuff is supposed to have a HP-UX license
> in the first place, for some version of HP-UX.)
>
> Is it legal to copy terminfo and termcap entries (from HP-UX in this
> case)?
I don't think it is illegal to tune any system to use HP hardware with a
published interface and I think the manual of the terminal clearly publishes
the codes as used in the termcap or terminfo files.
>
> The problem is that HP-UX is pretty much the only thing that comes with a
> terminfo entry for a 70096, and we have a bunch of those that could be
> useful on other systems too ... except that the scrollback doesn't work
> in the emulation modes.
Some settings of $TERM that come to mind include 'hpterm', 'hp700',
'hp70092'. I recal I've used them between HP-UX and Solaris machines, hence
Solaris also might have suitable termcap or terminfo entries.
>
> It would therefore be better to be able to run in native mode, but this
> pretty much _requires_ the terminfo/termcap entry ...
>
> Oh, and about the cursor keys on the 70096, if I were to put
> them in the
> "application" mode, would that help with bash et al.? They seem to be
> working in swinstall and such on HP-UX ... but the default
> mode seems to
> be non-transmitting, right? (yes, I could use that too myself, and
> re-enter stuff from the buffer with the print/enter key and do the
> line-modify thing... but the others have a hard time learning that.)
don't know, just put the terminal in em220 (vt220 emulation) mode to install
debian.
CBee
[-- Attachment #2: Type: text/html, Size: 3843 bytes --]
next reply other threads:[~2003-08-05 13:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-05 13:04 "Beerse, Corné" [this message]
2003-08-05 13:33 ` [parisc-linux] Terminfo/termcap for a 70096 Matthew Wilcox
2003-08-05 14:15 ` Nahkola Mikko
-- strict thread matches above, loose matches on Subject: below --
2003-08-05 13:53 "Beerse, Corné"
2003-08-05 18:38 ` John David Anglin
2003-08-05 11:37 Nahkola Mikko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=03Aug5.152448cest.119163@ns.hiscom.nl \
--to=c.beerse@torex-hiscom.nl \
--cc=mnahkola@trinms01.ntc.nokia.com \
--cc=parisc-linux@lists.parisc-linux.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox