From: Patrick McHardy <kaber@trash.net>
To: Arturo Borrero Gonzalez <arturo.borrero.glez@gmail.com>
Cc: Kevin Fenzi <kevin@scrye.com>,
Netfilter Development Mailing list
<netfilter-devel@vger.kernel.org>
Subject: Re: nftables/libnftables packages for Fedora
Date: Mon, 13 Jan 2014 00:25:33 +0000 [thread overview]
Message-ID: <20140113002533.GA3373@macbook.localnet> (raw)
In-Reply-To: <CAOkSjBhCTDCDzBLp86d1qA+xH=KMZtz2HrU3QfnZ+8AJ+qcWTg@mail.gmail.com>
On Sun, Jan 12, 2014 at 10:16:35PM +0100, Arturo Borrero Gonzalez wrote:
> On 12 January 2014 21:40, Kevin Fenzi <kevin@scrye.com> wrote:
> >
> > 2. There is some question about the /etc/nftables/* scripts. In Fedora
> > land, things in /etc/ should be config files, but these aren't really
> > config files. They call nft without a full path (/usr/sbin/nft, etc).
> > Should these really be in /usr/share ? or is it expected users will
> > modify them? Could you clarify the use case there?
> >
>
> There is a patch from me to address this:
> http://patchwork.ozlabs.org/patch/304866/
> Feel free to test it and comment.
>
> I have the same issue in the Debian land. I applied the patch locally
> in the package as a workaround.
>
> The patch is not applied yet to upstream.
Could you please resubmit? I'm going to apply it to the master branch.
Thanks.
next prev parent reply other threads:[~2014-01-13 0:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-12 20:40 nftables/libnftables packages for Fedora Kevin Fenzi
2014-01-12 21:16 ` Arturo Borrero Gonzalez
2014-01-13 0:05 ` Kevin Fenzi
2014-01-13 0:18 ` Patrick McHardy
2014-01-13 0:11 ` Kevin Fenzi
2014-01-15 9:53 ` Pablo Neira Ayuso
2014-01-15 10:18 ` Arturo Borrero Gonzalez
2014-01-13 0:25 ` Patrick McHardy [this message]
2014-01-13 0:17 ` Patrick McHardy
2014-01-13 0:29 ` Patrick McHardy
2014-01-13 8:54 ` Jan Engelhardt
2014-01-13 9:09 ` Patrick McHardy
2014-01-13 19:18 ` Kevin Fenzi
2014-01-14 8:55 ` Patrick McHardy
2014-01-14 18:28 ` Kevin Fenzi
2014-01-14 18:34 ` Pablo Neira Ayuso
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=20140113002533.GA3373@macbook.localnet \
--to=kaber@trash.net \
--cc=arturo.borrero.glez@gmail.com \
--cc=kevin@scrye.com \
--cc=netfilter-devel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).