Date: Fri, 22 Nov 1996 11:55:18 +0100 (MET) From: Greg Lehey <grog@lemis.de> To: ghelmer@cs.iastate.edu (Guy Helmer) Cc: freebsd-questions@freebsd.org Subject: Re: Has anyone ported hytelnet? Message-ID: <199611221055.LAA00568@freebie.lemis.de> In-Reply-To: <Pine.HPP.3.95.961119093323.7763A-100000@stimpy.cs.iastate.edu> from Guy Helmer at "Nov 19, 96 09:39:44 am"
next in thread | previous in thread | raw e-mail | index | archive | help
Guy Helmer writes: > I've been fooling around with getting hytelnet going on a friend's FreeBSD > 2.1.5 box for an upcoming Internet class he's running, and I'm having > problems getting hytelnet working properly -- it's having problems > displaying information as an apparent result of doing some things with > curses that it shouldn't. I've finally got it mostly working with > ncurses, but where an inverse text area marks the potential selection, the > inverse area appears with an annoying added <2> appended to the head and > tail of the inverse text. The termcap definition shouldn't be a problem > -- I was telnet'ed in from an xterm session, and every other full screen > app works fine... Even so, it looks *very* much like a termcap problem. > Maybe I just have a really old hytelnet source, but I haven't been able to > get into ftp.usask.ca to see if there's a newer version. Any suggestions > would be appreciated! Could it be that your hytelnet is reading the termcap definitions from a different place? termcap used to be in /etc/termcap, and later it got moved to /usr/share/misc/termcap. On my system, they're identical, but your mileage may vary. You may like to run ktrace against it (you'll need to have it enabled in the kernel by including 'options KTRACE'): ktrace -i -tn hytelnet kdump | more I don't have hytelnet, so I did it against vi instead. You'll see something like: === grog@freebie (/dev/ttyp5) /usr/home/grog 4 -> kdump 558 ktrace NAMI "/etc/malloc.conf" 558 ktrace NAMI "./vi" 558 ktrace NAMI "/home/grog/vi" 558 ktrace NAMI "/usr/bin/vi" 558 vi NAMI "/usr/libexec/ld.so" 558 vi NAMI "/var/run/ld.so.hints" 558 vi NAMI "/usr/lib/libcurses.so.2.0" 558 vi NAMI "/usr/lib/libcurses.so.2.0" 558 vi NAMI "/usr/lib/libtermcap.so.2.1" 558 vi NAMI "/usr/lib/libtermcap.so.2.1" 558 vi NAMI "/usr/lib/libtcl.so.75.1" 558 vi NAMI "/usr/lib/libtcl.so.75.1" 558 vi NAMI "/usr/lib/libm.so.2.0" 558 vi NAMI "/usr/lib/libm.so.2.0" 558 vi NAMI "/usr/lib/libc.so.3.0" 558 vi NAMI "/usr/lib/libc.so.3.0" 558 vi NAMI "/etc/malloc.conf" 558 vi NAMI "/home/grog/.termcap.db" 558 vi NAMI "/home/grog/.termcap.db" 558 vi NAMI "/home/grog/.termcap" 558 vi NAMI "/usr/share/misc/termcap.db" 558 vi NAMI "/usr/share/misc/termcap.db" These lines above show where vi looked for its termcap files. It didn't find them under /home/grog/.termcap.db, so it tried the next in line. 558 vi NAMI "/usr/share/vi/catalog/" 558 vi NAMI "/tmp" 558 vi NAMI "/tmp/bt.000558" 558 vi NAMI "/tmp/bt.000558" 558 vi NAMI "/etc/vi.exrc" 558 vi NAMI "/home/grog/.nexrc" 558 vi NAMI "/home/grog/.exrc" 558 vi NAMI "/tmp" 558 vi NAMI "/tmp/vi.000558" 558 vi NAMI "/var/tmp/vi.recover" 558 vi NAMI "/var/tmp/vi.recover" 558 vi NAMI "/var/tmp/vi.recover/vi.000558" 558 vi NAMI "/var/tmp/vi.recover/vi.000558" 558 vi NAMI "/tmp/vi.000558" 558 vi NAMI "/var/tmp/vi.recover/vi.000558" 558 vi NAMI "/tmp" 558 vi NAMI "/tmp/bt.000558" 558 vi NAMI "/tmp/bt.000558" 558 vi NAMI "/home/grog/.termcap.db" 558 vi NAMI "/home/grog/.termcap.db" 558 vi NAMI "/home/grog/.termcap" 558 vi NAMI "/usr/share/misc/termcap.db" 558 vi NAMI "/usr/share/misc/termcap.db" 558 vi NAMI "/tmp/vi.000558" 558 vi NAMI "/var/tmp/vi.recover/vi.000558" You'll notice some other interesting file names in this list; the technique is quite useful when you run into this kind of problem. Greg
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199611221055.LAA00568>