vmdebootstrap: confusing documentation of --systemd-networkd
Martin Pitt
mpitt at debian.org
Mon Nov 7 16:00:51 GMT 2016
Package: vmdebootstrap
Version: 1.7-1
Hello,
The manpage says
| --systemd-networkd
| Use Predictable Network Interface Names
|
| --no-systemd-networkd
| Do not use Predictable Network Interface Names using systemd-networkd.
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).
AFAIU the code, --systemd-networkd does
if self.settings['systemd-networkd']:
network.systemd_support(rootdir)
network.enable_systemd_resolved(rootdir)
and
def systemd_support(self, rootdir):
"""
Handle the systemd-networkd setting
"""
if self.settings['systemd-networkd']:
self.enable_systemd_networkd(rootdir)
else:
self.mask_udev_predictable_rules(rootdir)
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:
| --systemd-networkd
| Use networkd, resolved, and ifnames (predictable network interface names)
|
| --no-systemd-networkd
| Use ifupdown to manage eth0 and disable ifnames
Thanks for considering,
Martin
--
Martin Pitt | http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-systemd-maintainers/attachments/20161107/0fbdf6fd/attachment.sig>
More information about the Pkg-systemd-maintainers
mailing list