From owner-freebsd-current Tue Oct 1 05:19:38 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA14594 for current-outgoing; Tue, 1 Oct 1996 05:19:38 -0700 (PDT) Received: from spinner.DIALix.COM (root@spinner.DIALix.COM [192.203.228.67]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id FAA14586 for ; Tue, 1 Oct 1996 05:19:17 -0700 (PDT) Received: from spinner.DIALix.COM (peter@localhost.DIALix.oz.au [127.0.0.1]) by spinner.DIALix.COM (8.8.0/8.8.0) with ESMTP id UAA15170 for ; Tue, 1 Oct 1996 20:19:01 +0800 (WST) Message-Id: <199610011219.UAA15170@spinner.DIALix.COM> X-Mailer: exmh version 1.6.7 5/3/96 To: current@freebsd.org Subject: WARNING: botched ld.so commit! :-( Date: Tue, 01 Oct 1996 20:19:01 +0800 From: Peter Wemm Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk It's been pointed out to me that I managed to royally screw up my commit to the rtld/ld.so code, in just about the worst possible way on the only file in the entire system that's vulnerable to this type of screwup. (It's linked -Bsymbolic which allows undefined symbols) I'm still not entirely sure how it happened, but I think it was because I did the commits on a per-directory basis, and must have committed a slightly out of sync file from my last minute testing and "minor" tweaks after John and Nate went over it. I do remote commits, and must have committed from the wrong window/machine. If you get burned, you need to restore /usr/libexec/ld.so from somewhere, it doesn't matter how old as long as it's about 2.0.5 or later vintage. Getting a fixed version in place might be a challenge, you'll need to run "chflags noschg /usr/libexec/ld.so" to turn off the immutable bit and use some statically linked program to copy it in. (/bin/{cp,mv,rcp,pax} may be useful. Ouch... Sorry people, this was my fault and not something the review missed. -Peter