From owner-freebsd-stable Wed May 17 23:58:10 2000 Delivered-To: freebsd-stable@freebsd.org Received: from corinth.bossig.com (corinth.bossig.com [208.26.239.66]) by hub.freebsd.org (Postfix) with ESMTP id 49FBA37BC73 for ; Wed, 17 May 2000 23:58:06 -0700 (PDT) (envelope-from kstewart@3-cities.com) Received: from 3-cities.com (unverified [208.26.241.52]) by corinth.bossig.com (Rockliffe SMTPRA 4.2.1) with ESMTP id ; Wed, 17 May 2000 23:58:05 -0700 Message-ID: <39239474.F3BC619B@3-cities.com> Date: Wed, 17 May 2000 23:57:56 -0700 From: Kent Stewart Organization: BOSSig (BOSS Internet Group) X-Mailer: Mozilla 4.73 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Cy Schubert - ITSD Open Systems Group Cc: FreeBSD Stable Subject: Re: Strange Termcap behavior on 4.0-Stable References: <200005180513.e4I5DuP62924@cwsys.cwsent.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Cy Schubert - ITSD Open Systems Group wrote: > > In message <3923113A.8D37A144@3-cities.com>, Kent Stewart writes: > > When I telnet to two of my systems and su to root. The terminal setup > > for ansi or cons25 goes away. For example, if I do a > > "/usr/src/release/sysinstall/rtermcap ansi" as root, nothing appears. > > If I exit and do it on my original login, I see > > > > ansi|any ansi terminal with pessimistic > > assumptions:co#80:li#24:cl=50\E[;H\E[2J: > > bs:am:cm=\E[%i%d;%dH:nd=\E[C:up=\E[A:ce=\E[K:ho=\E[H:pt: > > > > This doesn't happen on my system with a buildworld of 10 May 2000. > > For the systems that you have the problem on, what date were they > CVSuped or built? This one doesn't work. It was cvsup'ed just before the build world. The world and kernel are from the same cvsup. Ruby was broken before this cvsup. I also cleaned /usr/obj (it had been linked before and I unlinked it) before I did the last set of builds. $ uname -a FreeBSD ruby.kbs.com 4.0-STABLE FreeBSD 4.0-STABLE #2: Tue May 16 17:38:23 PDT 2 000 root@ruby.kbs.com:/usr/src/sys/compile/RUBY i386 These work but have been left alone because of the problem. $ uname -a FreeBSD jade.kbs.com 4.0-STABLE FreeBSD 4.0-STABLE #11: Wed May 10 13:06:20 PDT 2000 root@jade.kbs.com:/usr/src/sys/compile/JADE i386 opal# uname -a FreeBSD opal.kbs.com 4.0-STABLE FreeBSD 4.0-STABLE #2: Sat May 13 02:47:42 PDT 2 000 root@opal.kbs.com:/usr/src/sys/compile/OPAL i386 > > > Something has happened and it really messes up trying to edit from a > > telnet session as root. The setup for xterm's still works but I can't > > telnet in from a Window's system. > > > > This also messes up building sysinstall. The generated code for the > > ansi and 5 or 6 cons.... is totally bogus and kills the compile. > > What does tset - -S display? On Ruby as root ruby# tset - -S ansi ansi ruby# On ruby as user $ tset - -S ansi ansi ansi:co#80:li#24:cl=50\E[;H\E[2J:bs:am:cm=\E[%i%d;%dH:nd=\E[C:up=\E[A:ce=\E [K:ho=\E[H:pt:$ on jade as root jade# tset - -S ansi ansi ansi:co#80:li#24:cl=50\E[;H\E[2J:bs:am:cm=\E[%i%d;%dH:nd=\E[C:up=\E[A:ce=\E [K:ho=\E[H:pt:jade# On Jade as user $ tset - -S ansi ansi ansi:co#80:li#24:cl=50\E[;H\E[2J:bs:am:cm=\E[%i%d;%dH:nd=\E[C:up=\E[A:ce=\E [K:ho=\E[H:pt:$ I thought Opal was broken but it looks like I could have been double telneted to ruby when I was having problems. When I first saw this, I thought I had a corrupted termcap.db but then I found I could edit as a user, just not as root. They are running different shells. My user shell is pdksh and I have left root as csh. It is almost like I have a permission problem somewhere. All three of these machines are conversions to 4.0 with clean installs. Ruby, which has the termcap problem, only runs FreeBSD 4.0-Stable. I can make sysinstall on the two systems but not on ruby. Kent -- Kent Stewart Richland, WA mailto:kstewart@3-cities.com http://www.3-cities.com/~kstewart/index.html http://daily.daemonnews.org/ SETI (Search for Extraterrestrial Intelligence) @ Home http://setiathome.ssl.berkeley.edu/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message