| 1 |
But what confuses me about that linked page is that from what I've heard |
| 2 |
from others here, option 1 - which is the option I think I'd prefer - |
| 3 |
requires more than just symlinking 80-net-name-slot.rules to |
| 4 |
/dev/null...? Apparently you should also create your own |
| 5 |
70-my-net-names.rules - but I've heard many people claim they used ethX |
| 6 |
names instead of netX names, so... again... should I just rename my file |
| 7 |
to 70-my-net-names.rules and leave the contents alone? |
| 8 |
|
| 9 |
Still confused/concerned about the differences in my current rules |
| 10 |
(items in mine that aren't in the examples)... |
| 11 |
|
| 12 |
|
| 13 |
|
| 14 |
On 2013-04-05 12:17 PM, William Hubbs <williamh@g.o> wrote: |
| 15 |
> You are right, there are several different ways to disable udev's |
| 16 |
> predictable network interface names: |
| 17 |
> |
| 18 |
> 1) add net.ifnames=0 to the kernel command line in your boot loader |
| 19 |
> configuration. |
| 20 |
> |
| 21 |
> 2) use any of the methods listed on the upstream wiki [1] under "I don't |
| 22 |
> like this, how do I disable this?" |
| 23 |
> |
| 24 |
> None of those should cause problems later. |
| 25 |
> |
| 26 |
> William |
| 27 |
> |
| 28 |
> [1] |
| 29 |
> http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames |
| 30 |
> |
Archives