Return to BSD News archive
Xref: sserve comp.os.386bsd.questions:15851 comp.os.386bsd.misc:4794 Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msunews!agate!howland.reston.ans.net!news.sprintlink.net!sundog.tiac.net!rick From: rick@vox.trystero.com (Richard E. Nickle) Newsgroups: comp.os.386bsd.questions,comp.os.386bsd.misc Subject: Re: FreeBSD 2.0 xterm problem Date: 12 Jan 1995 19:49:50 GMT Organization: The Trystero System Lines: 24 Message-ID: <3f414u$4d6@sundog.tiac.net> References: <3etrdn$get@cs5.cs.ait.ac.th> NNTP-Posting-Host: vox.trystero.com In article <3etrdn$get@cs5.cs.ait.ac.th>, Mano Pallewatta <pall@cs.ait.ac.th> wrote: |Hi, | I am using FreeBSD 2.0 and I find that xterms cannot run with |root permissions. Since xterms are SUID root normal users also cannot run |them unless SUID bit is removed. Then they are Ok. My H/W config. is 486 |DX 33 with 8 Meg and Cirrus Logic 5422 with 1 Meg. Initiall there was no |problem but this happened after sometime. I also notice that sometimes |cron and xterms die with signal 11 (Segmentation Violation). I don't seem to have this problem. The only problem I have with the XFree863.1 FreeBSD 2.0 port is that the xterm doesn't seem to interpret the -cr option correctly, either on the command line or in the resource database (this is the option that lets you set the cursor color). -- -- Richard Nickle http://www.trystero.com/rick.html