also sprach Michael Biebl <bi...@debian.org> [2014-10-07 15:12 +0200]: > No it is not enabled by default. Fwiw, you can trivially easily check > that yourself. (systemctl status and systemctl is-enabled is your friend).
Thank you for the hint. > > And the warning is there to remind the admin that s/he has to > > make changes now to accomodate the new, uninvited guest? > > It warns you, that the default systemd-networkd configuration > makes use of the new interface naming, but that it is not enabled. > Keep in mind, that this message is logged by systemd-udevd, not > systemd-networkd itself. So you get that irregardless whether > systemd-networkd is enabled/active or not. What is the rationale for this choice? Why did you guys decide it was best to log a warning every few seconds and require the admin to take action to restore the old behaviour? -- .''`. martin f. krafft <madduck@d.o> @martinkrafft : :' : proud Debian developer `. `'` http://people.debian.org/~madduck `- Debian - when you have better things to do than fixing systems chaos reigns within. reflect, repent, reboot. order shall return.
digital_signature_gpg.asc
Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)
