From: Patrick McHardy <kaber@trash.net>
To: "Jörg Thalheim" <joerg@higgsboson.tk>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH v2] add systemd service file
Date: Sat, 21 Mar 2015 17:45:33 +0000 [thread overview]
Message-ID: <20150321174532.GA16593@acer.localdomain> (raw)
In-Reply-To: <20150320105320.58266b67@turingmachine>
On 20.03, Jörg Thalheim wrote:
> The last PATCH was rejected, because it has added an integration script.
> This PATCH however only adds a service file, with no other dependency but the
> userpace nft program.
>
> my motivation was the following:
>
> - Providing a service file upstream hopefully lead to consistent behaviour across distributions
> - The people, who know how to deal with nft, are usually the upstream developer itself
> - The provided service should be reusable without any modification in any distribution
> and should preserve maintainers from reinventing the wheel all the time
> (debian currently does not provide atomic reloading in sid for example;
> archlinux does, but it doesn't set ProtectSystem and ProtectHome)
>
> I hope you can agree with this. Thanks
I'm think this is a good idea. However I don't know much about systemd
myself so please take care of Jan's suggestions first.
--
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-03-21 17:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-20 9:53 [PATCH v2] add systemd service file Jörg Thalheim
2015-03-20 10:25 ` Arturo Borrero Gonzalez
2015-03-21 17:45 ` Patrick McHardy [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-03-20 9:53 Jörg Thalheim
2015-03-20 11:06 ` Jan Engelhardt
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=20150321174532.GA16593@acer.localdomain \
--to=kaber@trash.net \
--cc=joerg@higgsboson.tk \
--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).