From owner-freebsd-security Wed Jun 26 20: 9:17 2002 Delivered-To: freebsd-security@freebsd.org Received: from ns1.pu.net (ns1.pu.net [216.87.139.234]) by hub.freebsd.org (Postfix) with ESMTP id C7B1437B418 for ; Wed, 26 Jun 2002 20:06:24 -0700 (PDT) Received: (from bugs@localhost) by ns1.pu.net (8.12.4/8.11.6) id g5R36FYK000640 for freebsd-security@freebsd.org; Wed, 26 Jun 2002 22:06:15 -0500 (CDT) (envelope-from bugs) From: Mark Hittinger Message-Id: <200206270306.g5R36FYK000640@ns1.pu.net> Subject: re: Legacy Static Linking (was: Security Advisory FreeBSD-SA-02:28.resolv) To: freebsd-security@freebsd.org Date: Wed, 26 Jun 2002 22:06:15 -0500 (CDT) X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > Roger Marquis wrote: > The track record of Unix and non-Unix operating > systems which no longer ship with statically linked binaries is > evidence they are no longer necessary. But it sure is handy to have some staticly linked binaries laying around in case you ruin your own /usr/lib. It has been known to happen! I keep statics of chflags, ed, fsck, fsdb, ls, mount, sh, tar, and umount in /ohno so that I can dig myself out. This is particularly important when trying to keep up with -current. For awhile there it was happening at least once every two weeks. Maybe -stable could go 100% dynamic but a few of us would go out of our way to keep some important tools staticly linked. Later Mark Hittinger bugs@pu.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message