From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/4818 Path: news.gmane.org!not-for-mail From: Laurent Bercot Newsgroups: gmane.linux.lib.musl.general Subject: Re: Re: MUSL_LIBRARY_PATH ? Date: Sun, 06 Apr 2014 21:27:10 +0100 Message-ID: <5341B89E.6060800@skarnet.org> References: <20140406161827.GY26358@brightrain.aerifal.cx> <53418C3B.8060700@skarnet.org> <20140406172254.GA26358@brightrain.aerifal.cx> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1396816050 31707 80.91.229.3 (6 Apr 2014 20:27:30 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 6 Apr 2014 20:27:30 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-4822-gllmg-musl=m.gmane.org@lists.openwall.com Sun Apr 06 22:27:24 2014 Return-path: Envelope-to: gllmg-musl@plane.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by plane.gmane.org with smtp (Exim 4.69) (envelope-from ) id 1WWtf1-0001Lu-Rw for gllmg-musl@plane.gmane.org; Sun, 06 Apr 2014 22:27:23 +0200 Original-Received: (qmail 7651 invoked by uid 550); 6 Apr 2014 20:27:20 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Original-Received: (qmail 7627 invoked from network); 6 Apr 2014 20:27:20 -0000 X-SourceIP: 109.255.124.30 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 In-Reply-To: <20140406172254.GA26358@brightrain.aerifal.cx> Xref: news.gmane.org gmane.linux.lib.musl.general:4818 Archived-At: On 06/04/2014 18:22, Rich Felker wrote: > Actually execline is not a solution for this, since the #! line that > invokes execline has to contain an absolute pathname to execline, > which is exactly the same problem we were trying to solve to begin > with: the need to install the program interpreter at a fixed absolute > pathname on a system you might not have root on. That will of course change when execline has conquered the world and is installed by every administrator at a standardized location. You're not helping me much with that goal here. :) > This can be avoided by using /usr/bin/env if you're willing to trust > that the env command is at that location and and the user adds > execline to their PATH, but that's fragile and adds yet another level > of indirection at program exec time... Yes, even /bin/sh is probably better than /usr/bin/env + another indirection. > The idea of the minimal static-linked binary as a solution is that it > would not need a program interpreter (dynamic linker or #! type) but > instead could do its own search (e.g. relative to its own binary) for > the dynamic linker to invoke. It's certainly the most efficient solution for any given binary, but it's less scalable - as in easy to maintain - than a script-based solution. -- Laurent