man: revert dynamic paths for split-usr setups This did not really work out as we had hoped. Trying to do this upstream introduced several problems that probably makes it better suited as a downstream patch after all. At any rate, it is not releaseable in the current state, so we at least need to revert this before the release. * by adjusting the path to binaries, but not do the same thing to the search path we end up with inconsistent man-pages. Adjusting the search path too would be quite messy, and it is not at all obvious that this is worth the effort, but at any rate it would have to be done before we could ship this. * this means that distributed man-pages does not make sense as they depend on config options, and for better or worse we are still distributing man pages, so that is something that definitely needs sorting out before we could ship with this patch. * we have long held that split-usr is only minimally supported in order to boot, and something we hope will eventually go away. So before we start adding even more magic/effort in order to make this work nicely, we should probably question if it makes sense at all.

man: generate configured paths in manpages In particular, use /lib/systemd instead of /usr/lib/systemd in distributions like Debian which still have not adopted a /usr merge setup. Use XML entities from man/custom-entities.ent to replace configured paths while doing XSLT processing of the original XML files. There was precedent of some files (such as systemd.generator.xml) which were already using this approach. This addresses most of the (manual) fixes from this patch: http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/tree/debian/patches/Fix-paths-in-man-pages.patch?h=experimental-220 The idea of using generic XML entities was presented here: http://lists.freedesktop.org/archives/systemd-devel/2015-May/032240.html This patch solves almost all the issues, with the exception of: - Path to /bin/mount and /bin/umount. - Generic statements about preference of /lib over /etc. These will be handled separately by follow up patches. Tested: - With default configure settings, ran "make install" to two separate directories and compared the output to confirm they matched exactly. - Used a set of configure flags including $CONFFLAGS from Debian: http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/tree/debian/rules Installed the tree and confirmed the paths use /lib/systemd instead of /usr/lib/systemd and that no other unexpected differences exist. - Confirmed that `make distcheck` still passes.

Reindent man pages to 2ch

man: fix link to systemd-networkd-wait-online.service in systemd-networkd.service(8)

resolved: add daemon to manage resolv.conf Also remove the equivalent functionality from networkd.

doc: typographical fine tuning

man: networkd typo fixes

networkd-wait-online: improve interoptability and enable by default To make sure we don't delay boot on systems where (some) network links are managed by someone else we don't block if something else has successfully brought up a link. We will still block until all links we are aware of that are managed by networkd have been configured, but if no such links exist, and someone else have configured a link sufficiently that it has a carrier, it may be that the link is ready so we should no longer block. Note that in all likelyhood the link is not ready (no addresses/routes configured), so whatever network managment daemon configured it should provide a similar wait-online service to block network-online.target until it is ready. The aim is to block as long as we know networking is not fully configured, but no longer. This will allow systemd-networkd-wait-online.service to be enabled on any system, even if we don't know whether networkd is the main/only network manager. Even in the case networking is fully configured by networkd, the default behavior may not be sufficient: if two links need to be configured, but the first is fully configured before the second one appears we will assume the network is up. To work around that, we allow specifying specific devices to wait for before considering the network up. This unit is enabled by default, just like systemd-networkd, but will only be pulled in if anyone pulls in network-online.target.

man: networkd - additional examples related to bridging

man: networkd - fix typo

man: networkd - mention resolv.conf symlink

man: refer to systemd.net{work,dev}(5) from systemd-networkd(8)

man: split out systemd.link(5) from udev(7)

man: networkd - clarify that multiple addresses/routes are supported

net-util: match on the driver as exposed by ethtool if DRIVER not set Also fix a copy-paste error that broke matching on interface name.

man: networkd typo fixes

man: suffix networkd config file options with "=" That's what we do for all options in the other man pages. It helps clarifying that these are options that values need to be assigned to.

.network/.netdev/.link: allow to match on architecture

man: networkd/udev - add to [Match] documentation

net-match: fix Driver= match It should match on the driver of the parent device.

man: minor fixes to networkd page Also enforce that we don't allow setting the Broadcast for IPv6 addresses.

doc: utilize the DocBook markup for some literals

doc: update punctuation Resolve spotted issues related to missing or extraneous commas, dashes.

networkd: VLAN - allow multiple vlans to be created on a link Also limit the range of vlan ids. Other implementations and documentation use the ranges {0,1}-{4094,4095}, but we use the one accepted by the kernel: 0-4094. Reported-by: Oleksii Shevchuk <alxchk@gmail.com>

networkd: netdev - rename Netdev to NetDev Both in the configuration file format and everywhere else in the code.

networkd: dhcpv4 - add notion of 'CriticalConnection' These connections are never torn down, even when the DHCP specifications say that they should be. This is useful/necessary when the rootfs (or another critical fs) is mounted over this network connection, and dataloss would result if the connection is lost. This option defaults to off, but our initrd generator (TBD) will enable it when applicable.

networkd: add basic VLAN support

networkd: add basic bonding support Refactor bridging support to be generic netdev support and extend it to cover bonding as well.

networkd: dhcp - by default ignore the MTU

sd-dhcp-client/networkd: add transient hostname support

sd-dhcp-client/networkd: add interface MTU support

networkd: DHCPv4 - allow opting out of using DNS servers Setting UseDNS=no will ignore any received DNS servers.

networkd: refuse to use .network files with missing Address/Gateway key These keys are mandatory in [Address]/[Route] sections. Otherwise, we hit an assert: ens3: setting addresses Assertion 'address->family == 2 || address->family == 10' failed at /build/amd64-generic/tmp/portage/sys-apps/systemd-9999-r1/work/systemd-9999/src/network/networkd-address.c:137, function address_configure(). Aborting. Reported-by: Alex Polvi <alex.polvi@coreos.com> At the same time make sure Route's Destination and Gateway uses the same address family.

Revert "net-util: add support for Type=ethernet" This reverts commit 4cd1214db6cf4b262e8ce6381bc710091b375c96. This may still be fixed in the kernel, revert this for now until we see how it all shakes out.

man: networkd - document DHCP option

net-util: add support for Type=ethernet When DEVTYPE is not set for a nic, it means it is a wired/ethernet device.

man: grammar and wording improvements This is a recurring submission and includes corrections to: - missing words, preposition choice. - change of /lib to /usr/lib, because that is what most distros are using as the system-wide location for systemd/udev files.

man: networkd - clarify Address/Gateway keys in [Network] section

networkd: add support for Route sections

man: networkd - document bridging

networkd: add support for [Address] sections This will allow specifying more options per address than the simple Address= entry in the [Network] section. Preliminary support for the same functionality for [Route] sections are added, but not yet hooked up, as more testing is needed.

networkd: don't filter on udev tags This removed the requirement for devices to be tagged with 'systemd-networkd' before they will be visible to networkd. Still, as by default we don't ship any .network files, network devices will simply be tracked, but not touched, unless the admin configures things explicitly.

build-sys: make networkd man pages conditional

man: networkd - add documentation