On 2013-04-02, Alan McKinnon <[email protected]> wrote: > On 02/04/2013 21:13, Paul Hartman wrote: >> On Mon, Apr 1, 2013 at 7:00 PM, Peter Humphrey <[email protected]> >> wrote: >>> The most important para to me in the news item was: "The feature can also be >>> completely disabled using net.ifnames=0 on the kernel command line." I just >>> added that to my grub.conf entries and I sail blissfully on with eth0. >> >> >> I updated remote virtual server (xen guest) and added this same >> option, crossed my fingers and rebooted, eth0 was still there and I >> was happy. >> > > > I did this to get exactly the same result: > > $ ls -al /etc/udev/rules.d/ > total 8 > drwxr-xr-x 2 root root 4096 Apr 1 15:10 . > drwxr-xr-x 4 root root 4096 Mar 30 20:34 .. > lrwxrwxrwx 1 root root 9 Apr 1 15:10 80-net-name-slot.rules -> /dev/null > > Like you, I happen to *like* eth0 and wlan0 on a laptop workstation > :-)
Sort of the same here, except that I use lan0 instead of eth0, because once in a while I use broadcom's wireless drivers instead of the kernel drivers, and the former assign an ethX name. Sadly, I still get some problems after resuming from hibernation: *sometimes*, the ethernet NIC won't be renamed lan0 (and remains eth0), and I have to rmmod and modprobe. Also sadly, the fact that several people go "oh noes you can't use wlan0" when I try to get comments on how to fix the issue does not help a lot... -- Nuno Silva (aka njsg) http://njsg.sdf-eu.org/
