Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!bunyip.cc.uq.oz.au!munnari.oz.au!news.Hawaii.Edu!ames!elroy.jpl.nasa.gov!swrinde!pirates.cs.swt.edu!cs.utexas.edu!not-for-mail From: Clarence.Chu@f132.n700.z6.ftn.air.org (Clarence Chu) Newsgroups: comp.os.386bsd.development Subject: FreeBSD-1.1.5.1(R) and X11 Date: 21 Jul 1994 22:50:15 -0500 Organization: UTexas Mail-to-News Gateway Lines: 32 Sender: nobody@cs.utexas.edu Message-ID: <774848838.AA00237@f74.n700.z6.ftn.air.org> NNTP-Posting-Host: news.cs.utexas.edu TO: dysonj hi dyson, i was trying to upgrade to 1.1.5.1R using the source patch on FreeBSD-1.1.5.1-RELEASE/1.1R-to-1.1.5.1R. before that X(11R6) run fine, after the upgrade, and even recompilation of X, whenever i bring up X, screen flash and the light of drive keep lighting up until i hit the keyboard few times. then the system reboot with page fault message and get into savecore. my /var area is too small to keep the image. i had acquired tarballs/srcdist/sys.* and had upgrade to another kernel. now, X behave differently: first invokation of X cause a SIGSEGV trapped by the Xserver, but subsequent invokation is okay. i.e. evethtime i reboot the system, i have to bring up X to wait for the death (SIGSEGV), and continual the X session. that's the story of upgradi to 1.1.5.1 from 1.1.0. i don't enough connection resource for transfering the whole 1.1.5.1 kit, but the upgrade shouldn't be there in case it's not stable enough. will that be caused by incomp implementation of setruid(3)? in the later case. there are still lots of work awaiting for to be done, like gcc-2.6.0, Fresco in R6, Motif internationisation after the 1.1.5.1, while i'm unable to get a stable kernel (st least one that can fire X11R6 without flaws), sigh! clarence chu ... * Origin: (6:700/132)