Age | Commit message (Collapse) | Author |
|
This restores logging that we had in the previous release, which has
proven useful in troubleshooting interface renaming problems.
|
|
In the new version of biosdevname (version 0.3.4), the default policy
generates interface names of the form "em1". That's not the naming
convention that we use. The "all_ethN" policy does use the traditional
ethernet naming convention.
(cherry picked from commit f05a91c02e27bb19717ddf8e1ffc07ed7b1bbbc5)
|
|
Bug 6445
Biosdevname program converts everything to eth devices.
|
|
Use existing config parser and perl to handle udev device naming.
Do renaming early in udev boot, and fixup config file later.
This avoids rescanning udev devices on boot and adds preliminary
support for hotplug.
|
|
Network interfaces are discovered at boot time in non-deterministic
order, so their names are non-deterministic. The vyatta_net_name
script is responsible for ensuring that network interface names are
changed to match their Vyatta config file entry when a match based on
MAC address is found. With this change, when a match is not found, we
use the biosdevname tool to to find the canonical name for an
interface, then change the interface's name to that name. This
ensures that NICs are named in a deterministic and systemmatic fashion.
|
|
|
|
|
|
Handle case where udev state file doesn't exist.
|
|
Several different cases were being handled incorrectly.
|
|
Replace references to VPL 1.0 with GPLv2
|
|
|
|
|
|
udev appears to be threaded where sub-scripts may be context switch;
so, defer config file interface updates to rl-system.init
|
|
This reverts commit b45bba4286e83f8babcd70eef908f2ea2f8fff3c.
|
|
silently write test BOOTFILE before trying too add/mod itf
|
|
|
|
|
|
|
|
|
|
|