Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!elroy.jpl.nasa.gov!swrinde!news.dell.com!natinst.com!hrd769.brooks.af.mil!hrd769.brooks.af.mil!not-for-mail From: burgess@hrd769.brooks.af.mil (Dave Burgess) Newsgroups: comp.os.386bsd.questions Subject: Re: Vt52 problem with vi on NetBSD 0.9 Date: 21 Sep 1993 20:33:01 -0500 Organization: Armstrong Laboratory, Brooks AFB, TX Lines: 50 Message-ID: <27oa0r$9rq@hrd769.brooks.af.mil> References: <1993Sep22.003221.23217@jupiter.sun.csd.unb.ca> NNTP-Posting-Host: hrd769.brooks.af.mil In article <1993Sep22.003221.23217@jupiter.sun.csd.unb.ca> douc@jupiter.sun.csd.unb.ca (D. Doucet) writes: > I am at something of a loss. I'm not sure if i'm doing >something wrong or if its something else. I just finished >upgrading from NetBSD 0.8 to 0.9 (which went very well). 0.8 >had no trouble talking to my vt52 terminal through com0. 0.9 >however, has problems when I try to run programs like vi or more >that use escape characters and what not. After these commands, I >get a bunch of reverse, block unprintables and so on. If I go to >the console and kill vi or more or whatever started the problem, >the prompt comes back and everything is fine. I had a similar problem the other day. It was also a completely different problem, but your letter remineded me of this. I compiled the latest gopher client/server. After I mangled my way through getting everything so that it would compile, I tried to run it, and it was like my terminal definitions were all messed up. I could not get the full screen capabilities of the client to work. No problem, says I, I will just switch to the console; that should work. Wanna bet??? It did exactly the same screwy stuff; square brackets splattered all over the place, and all kinds of similar strange stuff. It turns out that somewhere along the line, I had not updated my termcap library, and something was broke in the library/interface. I rebuilt ALL of the libraries, under the assumption that if one lib was toasted it was reasonable to assume that they all were. I also made the /usr/src/include stuff, just for good measure. Suffice it to say that everything is hunky-dory now. Gopher works like a charm. I even make up new Makefiles (Makefile.jol) and a new config.h (config.jol). I will be mailing the Makefile and config to the authors later, and I would gladly mail them out to anyone that needs them. Like I said, it is kind of like the original problem, but not. If there was a moral to this story, it would be to make sure that the executable, if it being rebuilt, is linked with the most current libraries and include files. -- ------ TSgt Dave Burgess NCOIC AL/Management Information Systems Office Brooks AFB, TX