On 23 July 2015 at 12:32, Michael Biebl bi...@debian.org wrote:
Am 23.07.2015 um 13:21 schrieb Dimitri John Ledkov:
If we in-vision that networkd is / will-be required on minimal
systems, I would want to have an alternative build available of
networkd nspawn with firewall support enabled.
Michael Biebl wrote:
We were reluctant to link against libiptc, since that would mean a
dependency on iptables, which is about 4M of additional disk space which
even minimal systems would have to install.
Given the recent upstream discussions [1] to switch to nftables, we will
probably wait
Am 02.06.2015 um 02:39 schrieb Michael Biebl:
Given the recent upstream discussions [1] to switch to nftables, we will
...
[1]
http://lists.freedesktop.org/archives/systemd-devel/2015-June/032661.html
That was the wrong link. Here's the correct one:
Joey Hess [2015-06-02 0:06 -0400]:
Michael Biebl wrote:
We were reluctant to link against libiptc, since that would mean a
dependency on iptables, which is about 4M of additional disk space which
even minimal systems would have to install.
Given the recent upstream discussions [1] to
Hi Joey
Am 02.06.2015 um 02:27 schrieb Joey Hess:
Package: systemd
Version: 220-3
Severity: normal
File: systemd-networkd
I'm trying to use systemd-networkd with systemd-nspawn --private-network
--port
now that a systemd supporting this feature has convenently landed in unstable
early.
