From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1756585AbcEaVr4 (ORCPT <rfc822;w@1wt.eu>);
	Tue, 31 May 2016 17:47:56 -0400
Received: from mail-io0-f169.google.com ([209.85.223.169]:35848 "EHLO
	mail-io0-f169.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1752935AbcEaVry (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Tue, 31 May 2016 17:47:54 -0400
MIME-Version: 1.0
Date: Tue, 31 May 2016 22:47:52 +0100
Message-ID: <CADcVQYsccqYkN9YbC3YXADtZ6MFyoninyeftkMH=K7SZ5CJpoA@mail.gmail.com>
Subject: script relative shebang
From: Boris Rybalkin <ribalkin@gmail.com>
To: linux-kernel@vger.kernel.org
Content-Type: text/plain; charset=UTF-8
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

Hi All,

I would like to know if any changes to parsing '#!' script header line
are accepted in particular having ability to run interpreter from
relative to the script path?

Something like:

#!{dirname}/python/bin/python

Where {dirname} is a special keyword replaced with dirname of a script.

This is useful for apps which bring dependencies with them and do not
want to hardcode absolute paths as target fs layout is not known or
has to be flexible.

As I understand the implementation is here and I could probably provide a patch:
fs/binfmt_script.c

Sorry if this is not the right place to discuss these things.

Thank you.


--
Boris Rybalkin
ribalkin@gmail.com