29e60882ca
Previously, configuring and enabling network interfaces failed with: "The following SSH command responded with a non-zero exit status. Vagrant assumes that this means the command failed! /usr/sbin/biosdevname --policy=all_ethN -i bash: /usr/sbin/biosdevname: No such file or directory Stdout from the command: bash: /usr/sbin/biosdevname: No such file or directory" The previous attempt to fix this (ccc4162) doesn't work since it doesn't properly parse the 'bash: /usr/sbin/biosdevname: No such file or directory' error message. This patch works around that problem and adds a comment explaining the meaning of the return codes.
Vagrant Core Plugins
These are plugins that ship with Vagrant. Vagrant core uses its own plugin system to power a lot of the core pieces that ship with Vagrant. Each plugin will have its own README which explains its specific role.