| 1 |
On 06/04/2013 17:57, Alan Mackenzie wrote: |
| 2 |
>> Please excuse me, I am running back and forth from the servers and |
| 3 |
>> > typing the error message here. Did our configuration get switched to |
| 4 |
>> > IP6? These are our DB servers and why me!!! Why ME!!!!! |
| 5 |
> No, it's not just you, it's happened to pretty much everybody. udev-200 |
| 6 |
> now renames eth0, eth1, .... |
| 7 |
|
| 8 |
Please please PLEASE, for the love of god joseph mary and every other |
| 9 |
$DEITY on the planet |
| 10 |
|
| 11 |
STOP SPREADING THIS FUD |
| 12 |
|
| 13 |
It did not happen to pretty much everybody. It happened to people who |
| 14 |
blindly updated thignsd and walked away, who did not read the news |
| 15 |
announcement, who did not read the CLEARLY WORDED wiki article at |
| 16 |
freedesktop.org or alternatively went into mod-induced panic and started |
| 17 |
making shit up in their heads. |
| 18 |
|
| 19 |
@Nick: |
| 20 |
|
| 21 |
all you have to do is run eselect news and read what is there. It is all |
| 22 |
very clearly worded and makes complete sense when read in conjunction |
| 23 |
with the wiki page (link is in the news statement). |
| 24 |
|
| 25 |
Unless you have a very complex setup with multiple NICs (and especially |
| 26 |
if they are USB based) you will find that the docs probably cover your |
| 27 |
case completely (just add common sense and a bit of understanding about |
| 28 |
what udev does on a Linux system). |
| 29 |
|
| 30 |
All that happened is that the thing you used to know as eth0 now has a |
| 31 |
different name. |
| 32 |
The most important thing you need to remember is you cannot safely |
| 33 |
rename that NIC to ethX as this can collide with what the kernel drivers |
| 34 |
are trying to do. And that is all that happened here. |
| 35 |
|
| 36 |
-- |
| 37 |
Alan McKinnon |
| 38 |
alan.mckinnon@×××××.com |
Archives