Bug#407460: USB ethernet interface renamed after installation on NSLU2 which causes the system to be inaccessible
On 2/12/07, Marco d'Itri <email@example.com> wrote:
> being added on my test system, does this tells whether something like
> DRIVERS=="?*" is matching or not ?
Apparently not. I see that I already suggested this in my first
reply on december 14.
Yeah, your comment in your previous email is what prompted me to ask
the question :-)
> It seems that the real question is what sequence of events causes an
> interface to be named eth1_rename, as opposed to the next available
> interface name (e.g. eth1). I'll see if I can figure this out from the
I explained this today.
Ok, I thought that you meant that the interface would be renamed to
the next available interface name e.g. 'eth0' would become 'eth1', not
'eth1_rename'. Sorry for the misunderstanding.
I do not think I can help you further if you ignore what I write.