From owner-freebsd-hackers Mon Jul 24 18:23:56 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id B30D737B7D2 for ; Mon, 24 Jul 2000 18:23:53 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id SAA11608; Mon, 24 Jul 2000 18:23:23 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id SAA04929; Mon, 24 Jul 2000 18:23:22 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Mon, 24 Jul 2000 18:23:22 -0700 (PDT) Message-Id: <200007250123.SAA04929@vashon.polstra.com> To: hackers@freebsd.org Reply-To: hackers@freebsd.org Cc: jazepeda@pacbell.net Subject: Re: ELF rtld and environment variables... In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Alex Zepeda wrote: > > Uck. Glad you liked the idea! :-) > I'm curious, why do a.out/FreeBSD-elf/Linux-elf programs all respond to > the same variables? Sure it's perhaps a consistant interface, but > wouldn't somthing like LINUX_LD_LIBRARY_PATH and/or AOUT_LD_LIBRARY_PATH > make more sense? Well, there is a different reason for each of the dynamic linkers. FreeBSD ELF: It's required by the ELF specification. FreeBSD a.out: Backward compatibility. Linux ELF: Because it's part of Linux and that's just what it does. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message