| 1 |
On Sat, Apr 06, 2013 at 10:25:50AM -0400, Tanstaafl wrote: |
| 2 |
> On 2013-04-05 4:11 PM, William Hubbs <williamh@g.o> wrote: |
| 3 |
> > On Fri, Apr 05, 2013 at 02:38:21PM -0500, Bruce Hill wrote: |
| 4 |
> >> Just dealing with one server and my Linux router, they've been updated to |
| 5 |
> >> sys-fs/udev-200 and are both still using the same |
| 6 |
> >> /etc/udev/rules.d/70-persistent-net.rules file they've had for over a year, |
| 7 |
> >> which was working with udev-171. |
| 8 |
> > |
| 9 |
> > Do you have your network interface drivers built into the kernel or are |
| 10 |
> > they modules? |
| 11 |
> |
| 12 |
> I'm very interested in the significance of this question... |
| 13 |
> |
| 14 |
> My server is module free, so all drivers are built into the kernel. |
| 15 |
|
| 16 |
The significance is that the kernel determines the eth* name order. |
| 17 |
Right now, you are lucky in that the order is what you think it should |
| 18 |
be, but if something changes in the kernel causing your cards to be |
| 19 |
initialized in a different order, you will not be allowed to swap them |
| 20 |
around in the eth* name space, e.g. eth1 can't become eth0 or visa |
| 21 |
versa. |
| 22 |
|
| 23 |
That is why it is recommended that you use something like net0, net1, |
| 24 |
etc for your interface names. |
| 25 |
|
| 26 |
William |
Archives