Problems with vi, dvips, xmcd in kernel 2.0.0

Problems with vi, dvips, xmcd in kernel 2.0.0

Post by Open Access Technology Int' » Thu, 20 Jun 1996 04:00:00



Upon upgrading to 2.0.0 as well as upgrading virtually everything
as recommended in the Changes notes, I have the following problems:

1. vi seems to want to add unwanted characters (that do disappear
    upon saving or ^L, but are annoying). This I think is due to
    use of termcap-2.0.8.
2. dvips fails with a segmentation fault (latex seems to be OK). It is
   after running*and when trying to get a .ps file with dvips
   that it fails.
3. xmcd, the cd player, also fails. It also gives a lot of iocntrl
   errors.

Has anyone one seen similar behavior? Any suggestions?

Thanks,

G. Irisarri

 
 
 

Problems with vi, dvips, xmcd in kernel 2.0.0

Post by bonni mierzejews » Thu, 20 Jun 1996 04:00:00




>1. vi seems to want to add unwanted characters (that do disappear
>    upon saving or ^L, but are annoying). This I think is due to
>    use of termcap-2.0.8.

Yep.  Pick up termcap-2.0.8.fix at any Sunsite mirror and replace
/etc/termcap with it.  This will put you back in business.

bonni
coming soon - 1996 IF Competition entry
C++ Turbo Vision archive: http://brooks.wvn.wvnet.edu/tvhome
__   __
IC | XC  |   bonni mierzejewska "The Lone Quilter"

NI | KA  | Kelly's Creek Homestead, Maidsville, WV

 
 
 

Problems with vi, dvips, xmcd in kernel 2.0.0

Post by Andreas Dilg » Thu, 20 Jun 1996 04:00:00




Quote:>Upon upgrading to 2.0.0 as well as upgrading virtually everything
>as recommended in the Changes notes, I have the following problems:

>1. vi seems to want to add unwanted characters (that do disappear
>    upon saving or ^L, but are annoying). This I think is due to
>    use of termcap-2.0.8.

I have had the same problem on two separate systems, and the problem is
related to the xterm entry in /etc/termcap. I tried adding the missing
xterm settings from my old termcap to the new one, but they didn't fix
the problem.  As I don't know muchmore than the basic termcap settings,
I can't really say which one is the culprit.  I ended up copying my old
xterm termcap entry (from 2.0.0) into the new file, and it seems to work
OK again.  Here it is:

---
xterm|vs100|xterm terminal emulator (X window system):\
        :do=^J:le=^H:ho=\E[H:\
        :co#80:li#65:cl=\E[H\E[2J:bs:am:cm=\E[%i%d;%dH:nd=\E[C:up=\E[A:\
        :ce=\E[K:cd=\E[J:so=\E[7m:se=\E[m:us=\E[4m:ue=\E[m:\
        :md=\E[1m:mr=\E[7m:me=\E[m:\
        :ku=\EOA:kd=\EOB:kr=\EOC:kl=\EOD:kb=^H:\
        :k1=\EOP:k2=\EOQ:k3=\EOR:k4=\EOS:pt:sf=\n:sr=\EM:\
        :al=\E[L:dl=\E[M:im=\E[4h:ei=\E[4l:mi:dc=\E[P:\
        :MT:ks=\E[?1h\E=:ke=\E[?1l\E>:xn:\
        :AL=\E[%dL:DL=\E[%dM:DC=\E[%dP:\
        :hs:ts=\E[?E\E[?%i%dT:fs=\E[?F:es:ds=\E[?E:\
        :is=\E\E[m\E[?7h\E[?1;4l:cs=\E[%i%d;%dr:\
        :rs=\E[r\E<\E[m\E[H\E[2J\E[?7h\E[?1;3;4;6l:
---

Cheers, Andreas.
--
Andreas Dilger   University of Calgary  \"If a man ate a pound of pasta and
(403) 220-8792   Micronet Research Group \ a pound of antipasto, would they
Dept of Electrical & Computer Engineering \   cancel out, leaving him still
http://www-mddsp.enel.ucalgary.ca/People/adilger/       hungry?" -- Dogbert

 
 
 

1. dvips segfaults with new kernel

I had a Linux Slackware installation, the one obtainable
by ftp from sunsite.unc.edu in Oct./Nov. '95 (Slackware 3.1?).
I.e., kernel 1.2.13, libc.so.5.0.9, libm.so.5.0.0, ld.so.1.7.3,
Elf system.
Recently I upgraded to kernel 2.0.30, libc.so.5.4.33, libm.so.5.0.9,
ld(-linux).so.1.8.10. The links and file placements are correct
according to the ELF-HOWTO. However, I have kept the LaTeX version
from the previous installation, including dvips.

And when I now runs dvips, it says:
     This is dvipsk 5.58a (and so on)
     Segmentation fault
Rebooting with the old kernel, however, I can still use the old
dvips (although of course other things like the new modules do not
work with the old kernel).

How comes?
And can I do anything to avoid the segfault, other than installing
LaTeX/dvips anew?

:)  Ingjald Finjord

2. compiling glibc-2.1.1 and libc-lock.h not found

3. vi and lp problems after upgrade to kernel 2.0.0

4. funny mount problem

5. supraexpress modems (28.8) problems w/dial-ins

6. No Carrier

7. Netscape plug-ins problem

8. RH 5 (libc6 vs libc5 problem): Program works, but ldd says "not found". Why?

9. Problems with dialing out when dial-ins are enabled

10. Netscape 4.51 and plug-ins problem

11. Problem with Solaris 5.7 and xmcd

12. xmcd problem on linux

13. XMCD problem...