cloud-initramfs-dyn-netconf takes klibc ipconfig output and writes /etc/network/interfaces (ENI) style file in /run/network/dynamic-interfaces.
The goal is to have the user's provided 'ip=' kernel parameters be "sticky" and not have the network interface get bounced by normal post-initramfs networking bringup. Essentially kernel command line should override /etc/network/interfaces in a similar way to command line flags overriding environment or system configuration.
As it is right now, we have to have ln -sf /etc/network/interfaces /run/network/dynamic-interfaces in order for this to work.
That means:
a.) if you've not done this, dyn-netconf isn't much use
b.) if you *have* done this, but not provided ip= then you'll get you'll get no network configuration.
See [1] for doc on cloud-initramfs -dyn-netconf.
cloud-initramfs -dyn-netconf takes klibc ipconfig output and writes /etc/network/ interfaces (ENI) style file in /run/network/ dynamic- interfaces. interfaces in a similar way to command line flags overriding environment or system configuration.
The goal is to have the user's provided 'ip=' kernel parameters be "sticky" and not have the network interface get bounced by normal post-initramfs networking bringup. Essentially kernel command line should override /etc/network/
As it is right now, we have to have ln -sf /etc/network/ interfaces /run/network/ dynamic- interfaces in order for this to work.
That means:
a.) if you've not done this, dyn-netconf isn't much use
b.) if you *have* done this, but not provided ip= then you'll get you'll get no network configuration.
-- bazaar. launchpad. net/~cloud- initramfs- tools/cloud- initramfs- tools/trunk/ view/head: /dyn-netconf/ doc/README. txt
[1] http://