From owner-freebsd-current Sun Aug 27 17: 8:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from mta6.snfc21.pbi.net (mta6.snfc21.pbi.net [206.13.28.240]) by hub.freebsd.org (Postfix) with ESMTP id 4FEC037B423 for ; Sun, 27 Aug 2000 17:08:30 -0700 (PDT) Received: from pacbell.net ([63.199.30.65]) by mta6.snfc21.pbi.net (Sun Internet Mail Server sims.3.5.2000.01.05.12.18.p9) with ESMTP id <0FZZ009LN6Z5FA@mta6.snfc21.pbi.net> for current@freebsd.org; Sun, 27 Aug 2000 17:06:42 -0700 (PDT) Date: Sun, 27 Aug 2000 17:07:18 -0700 From: "George W. Dinolt" Subject: Linux ABI no longer supports staroffice To: Marcel Moolenaar Cc: current@freebsd.org Message-id: <39A9AD36.D3CAECDA@pacbell.net> MIME-version: 1.0 X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.12 i386) Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit X-Accept-Language: en Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Marcel: Up until this weekend, I was able to use the staroffice52 port with little problem (I had installed it earlier without benefit of the port and it worked fine.) I did a 5.0-current kernel rebuild on Thursday with sources current on that day and things were fine. When I rebuilt my kernel yesterday afternoon with sources from Saturday morning, the port stopped working. I get the following error messages I18N: X Window System doesn't support locale "C" _X11TransSocketOpen: socket() failed for local _X11TransSocketOpenCOTSClient: Unable to open socket for local _X11TransOpen: transport open failed for local/dinolt1.bingdrive:0 setup.bin: cannot open display ":0.0" Please check your "DISPLAY" environment variable, as well as the permissions to access that display (See "man X" resp. "man xhost" for details) I am running the install as root. The Window Manager is up and running, other programs including linux-netscape have no trouble running in the same environment. This is not a clue for me, but it may mean something to others. (By the way, these errors did not appear prior to the changes.) I was wondering whether the setrlimit changes had something to do with this. This seems to be the major change to the linux code in the last few days. Apparently you were the one to make those changes, so I am writing to you (Marcel) Anyway, thought someone should know. George Dinolt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message