From: Patrick McHardy <kaber@trash.net>
To: Arturo Borrero Gonzalez <arturo.borrero.glez@gmail.com>
Cc: Sam Liddicott <sam@liddicott.com>,
Netfilter Development Mailing list
<netfilter-devel@vger.kernel.org>
Subject: Re: [nft PATCH] files: replace interpreter during installation
Date: Wed, 22 Jan 2014 16:51:06 +0000 [thread overview]
Message-ID: <20140122165105.GA18994@macbook.localnet> (raw)
In-Reply-To: <CAOkSjBidi2YdLuQaqDBOTDuMVHRPCVnhJFa2zRzpyfEgbQyA8w@mail.gmail.com>
On Wed, Jan 22, 2014 at 05:45:39PM +0100, Arturo Borrero Gonzalez wrote:
> On 14 January 2014 16:16, Patrick McHardy <kaber@trash.net> wrote:
> > On Tue, Jan 14, 2014 at 03:00:14PM +0000, Sam Liddicott wrote:
> >> I realise a solution is reached, but an alternative in common use is
> >> mentioned here for completeness;
> >>
> >> #! /usr/bin/env nft -f
> >>
> >> it is commonly used to invoke interpreters whose path is unknown but
> >> which can be expected to be on the PATH
> >
> > I'm find either way. Unless there are arguments for not using env,
> > this seems like the simpler fix.
>
>
> Using env with an additional argument (the '-f') seems to fail in my system.
>
> ===8<===
> #!/usr/bin/env nft -f
> list table filter
> ===8<===
>
> % ./test
> /usr/bin/env: nft -f: No such file or directory
I guess lets just keep it this way. Thanks.
next prev parent reply other threads:[~2014-01-22 16:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-13 9:16 [nft PATCH] files: replace interpreter during installation Arturo Borrero Gonzalez
2014-01-13 9:39 ` Patrick McHardy
2014-01-13 9:49 ` Arturo Borrero Gonzalez
2014-01-13 9:52 ` Patrick McHardy
2014-01-13 16:30 ` Alex Elsayed
2014-01-14 12:48 ` Arturo Borrero Gonzalez
2014-01-14 13:11 ` Patrick McHardy
2014-01-14 15:00 ` Sam Liddicott
2014-01-14 15:16 ` Patrick McHardy
2014-01-22 16:45 ` Arturo Borrero Gonzalez
2014-01-22 16:51 ` Patrick McHardy [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-12-24 1:21 Arturo Borrero Gonzalez
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140122165105.GA18994@macbook.localnet \
--to=kaber@trash.net \
--cc=arturo.borrero.glez@gmail.com \
--cc=netfilter-devel@vger.kernel.org \
--cc=sam@liddicott.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.