Bug#843542: vmdebootstrap: confusing documentation of --systemd-networkd

[Sunil Mohan Adapa]

On Monday 07 November 2016 09:30 PM, Martin Pitt wrote:
[...]
> But this is very confusing -- networkd has nothing at all to do with
> predictable network interface naming. This is done by udev, and
> happens independently of networkd (or NM, or ifupdown).
[...]
> So in addition this also enables resolved (which is again an
> independent component). So IMHO these options should either be split
> into --enable-networkd, --enable-resolved, and --disable-ifnames; or
> (this presumably makes more sense) the documentation should be
> clarified to something like:

When building FreedomBox images, we ran into issue with name resolution
inside images being built and wanted to turn off systemd-resolved.
However, turning off system-networkd is the only way to do this and this
also disabled persistent naming of network interfaces which is an
important feature for us.

Please consider splitting the '--systemd-networkd' option into three
separate options (especially the persistent naming).

-- 
Sunil

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 858 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-systemd-maintainers/attachments/20170307/8f20fa6d/attachment-0001.sig>