[431] in arla-drinkers
Re: arla 0.20: getcwd & XFS panics
daemon@ATHENA.MIT.EDU (Brandon S. Allbery KF8NH)
Fri Dec 25 19:03:02 1998
From owner-arla-drinkers@stacken.kth.se Sat Dec 26 00:03:01 1998
Return-Path: <owner-arla-drinkers@stacken.kth.se>
Delivered-To: arla-drinkers-mtg@bloom-picayune.mit.edu
Received: (qmail 11182 invoked from network); 26 Dec 1998 00:02:58 -0000
Received: from unknown (HELO sundance.stacken.kth.se) (130.237.234.41)
by bloom-picayune.mit.edu with SMTP; 26 Dec 1998 00:02:58 -0000
Received: (from majordom@localhost)
by sundance.stacken.kth.se (8.8.8/8.8.8) id AAA04209
for arla-drinkers-list; Sat, 26 Dec 1998 00:58:28 +0100 (MET)
Received: from hilfy.ece.cmu.edu (root@HILFY.ECE.CMU.EDU [128.2.253.106])
by sundance.stacken.kth.se (8.8.8/8.8.8) with ESMTP id AAA04204
for <arla-drinkers@stacken.kth.se>; Sat, 26 Dec 1998 00:58:24 +0100 (MET)
Received: from speaker.kf8nh.apk.net (root@ANNEX-2.SLIP.ECE.CMU.EDU [128.2.236.2])
by hilfy.ece.cmu.edu (8.8.8/8.8.8) with ESMTP id SAA11371;
Fri, 25 Dec 1998 18:58:20 -0500 (EST)
Received: from rushlight.kf8nh.apk.net (allbery@rushlight.kf8nh.apk.net [10.9.204.1])
by speaker.kf8nh.apk.net (8.8.7/8.8.7) with ESMTP id SAA14109;
Fri, 25 Dec 1998 18:58:20 -0500
Received: (from allbery@localhost)
by rushlight.kf8nh.apk.net (8.8.7/8.8.7) id SAA00824;
Fri, 25 Dec 1998 18:58:17 -0500
Message-Id: <199812252358.SAA00824@rushlight.kf8nh.apk.net>
X-Mailer: exmh version 2.0.2 2/24/98
To: Max <maxk@chinook.stanford.edu>
cc: allbery@kf8nh.apk.net (Brandon S. Allbery KF8NH),
arla-drinkers@stacken.kth.se
Subject: Re: arla 0.20: getcwd & XFS panics
In-reply-to: Your message of "Fri, 25 Dec 1998 13:18:43 PST."
<E0zted9-0000Po-00@chinook.stanford.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 25 Dec 1998 18:58:16 -0500
From: "Brandon S. Allbery KF8NH" <allbery@kf8nh.apk.net>
Sender: owner-arla-drinkers@stacken.kth.se
Precedence: bulk
In message <E0zted9-0000Po-00@chinook.stanford.edu>, Max writes:
+-----
| You (Brandon S. Allbery KF8NH) wrote:
| > In message <E0ztLNz-0000Ys-00@chinook.stanford.edu>, Max writes:
| > | I just compiled Arla 0.20 and noticed some major problems. The first
| > | mistake was copying getcwd.so to /lib. I did this with all the other
| > | versions with no major problems. My /etc/ld.so.preload has been
| > +--->8
| >
| > You didn't pay attention to the instructions, then. Overwriting a shared
| > library that's in use is fatal in Linux; the install instructions in the
| > announcement specifically stated that you need to rename the existing
| > getcwd.so, then copy the new one in, so the running copy isn't overwritten.
|
| This was never a problem with the old getcwd, I've been doing this
| ever since version 0.14 came out. I also didn't see any mention of
+--->8
The source, and therefore the code/data/BSS in the generated object, didn't
change in any of those versions; so you were "safe" by luck. Conceivably
just using a different compiler to build the same source could have caused
the same result, though.
| this in either INSTALL, README, or NEWS. Where are these instructions
| that you are referring to?
+--->8
They were in the announcement of the 0.20 version. If they weren't included
in the distribution files, that was an oversight on someone's part.
| > | log in and remove getcwd.so from ld.so.preload. Until I did that, I
| > | couldn't start X (it complained about a missing __getcwd symbol).
| >
| > Is your X server (or wrapper) linked against glibc2/libc6 or libc5? If
| > glibc2, what version? In glibc-2.0.x, __getcwd is the real getcwd() call;
| > getcwd is a weak symbol, so that it can be redefined in exactly the way the
| > replacement getcwd.so does while leaving the original available. Or should
|
| > be. It's working here (Red Hat 5.2, glibc-2.0.7) but I have no Debian
| > systems to compare against.
|
| The X server is linked against glibc-2.0.7u (or at least it should
| be).
+--->8
Hm. Can you determine exactly which program is producing the symbol error?
In Red Hat it could be any of: xinit, Xwrapper, the X server itself, or the
window manager (which would cause the X server to shut down immediately).
--
brandon s. allbery [os/2][linux][solaris][japh] allbery@kf8nh.apk.net
system administrator [WAY too many hats] allbery@ece.cmu.edu
carnegie mellon / electrical and computer engineering KF8NH
We are Linux. Resistance is an indication that you missed the point.
