Am Tue, 2 Apr 2013 20:31:10 +0000 (UTC) schrieb Grant Edwards <grant.b.edwa...@gmail.com>:
> On 2013-04-02, Alan McKinnon <alan.mckin...@gmail.com> wrote: > > > No, you are stilling misunderstanding. > > He's not the only one. > > > The news item goes to great lengths to explain that there is a new > > way and it is different from the old way. > > I did grok that much. I had a 70-persistent-net.rules file that named > my three interfaces "eth0" "eth1" and "eth2" based on their MAC > addresses. After reading the news item and flameeyes blog, I was still > pretty much at a loss regarding what I was actually supposed to _do_. AFAIU, as soon as the names in your rules file differ from the in-kernel names (e.g., if the kernel switches eth0 and eth1), bad things can happen during renaming, due to deadlocks or something like that (others will have understood it better and should explain it rather than I). So, again AFAIU, it's enough to change the network device names from eth* to net*, or whatever you desire (I went with Flameeyes naming scheme). The important thing is that your device names *don't* use the in-kernel namespace "eth*". See section 3 "Old interface naming rules" in the news item and the references therein. The new default naming scheme is AFAICT orthogonal to that. HTH -- Marc Joliet -- "People who think they know everything really annoy those of us who know we don't" - Bjarne Stroustrup
signature.asc
Description: PGP signature
