Originally Posted by llrainey
You do have to add the biosdevname=0 to the end of the kernel line in /etc/grub/menu.lst but that alone does not fix the issue
You have to edit /etc/udev/rules.d/70-persistent-net-rules and change the em0 (or whatever it change to to the name you wanted - in my case eth0 and eth1
Thank you. Your recommendations have worked for me, but I've found that I was able to cut out one of the steps. For anyone else who may be interested, please bear in mind the following: I am performing these steps on the system that I described in my earlier posts, where I have added/removed packages and added/removed kernel commands. In that respect, consider my system 'tainted', and consider the following as something that worked for me, but may or may not work for you.
I was able to get back to eth0 and eth1 by simply deleting the following file:
Note that the filename differs slightly from that described previously, as there was a typo in the original file name. In between 'net' and 'rules' there should be a period, not a dash.
I examined the persistent net rules file and confirmed that it contained no rules other than the two offensive rules that were renaming my net interfaces. So I simply deleted the file and rebooted. Upon reboot, ifconfig confirmed that everything was back to normal.
Additionally, I removed the kernel command line entry in grub.conf, so that 'biosdevname=0' is no longer there. After rebooting, everything works as expected.
I imagine that there are a limited number of entities in your locale that have 1000 or more PCs to administer. Thank you for your help.
I also administrate a fair number of computers, I am also very security conscious, and I also lock-down systems so that access highly restricted. Methods include recognition by IP address, port, MAC address, device name, etc.
I am also disappointed to see such sweeping changes as these being implemented with such gratuitous disregard for the effects on the user base. The person behind this ethernet device renaming business works at Dell. Evidently, someone has decided that what is good for Dell is good for everyone, and they rushed ahead with reckless abandon. Perhaps if an entity such as Wal*Mart weighed in with it's critical mass, someone might re-think their decisions.
One of the things that I really dislike about Windows 7 is that it makes too many decisions for the user, and effectively serves to isolate the user from the hardware. When an OS designer makes the decision to make pre-defined selections for user choices, the effect is to make a lot of assumptions about what users want (or should want), and some of the time these assumptions are going to be inaccurate. The more assumptions that are made, the more inaccurate decisions become forced upon the user. When these choices cannot be easily undone, the user becomes trapped by the OS.
Eventually this process results in so many decisions being made that the user becomes isolated from the hardware, and the software ends up making all of the hardware-based decisions. Whether or not that is a good or a bad thing depends entirely upon how well the OS designer has anticipated what all users want. As more decisions are made on behalf of the user, the likely it becomes that decisions will be made that adversely effect an increasing number of users. Eventually, everyone is forced to accept things being done one way. That's the way of Windows. Linux users are traditionally a group of people who don't like being forced to do things one way. Linux users have traditionally resisted such forced measures, frequently reciting the mantra, "Linux is about CHOICE." Well, looking at the writing on the wall, it may not be about choice any more.
My evaluation of Windows 7 is that as an expert user, I am no longer able to configure the OS to do what I want it to do. Too many decisions that have been made to palliate the anticipated desires of uninformed users. How to un-do these behaviors are trade secrets. The OS inner workings are not well documented. You have to buy somebody's book to learn how to undo them.
It's disappointing to see Fedora starting to drag Linux down that road. Unless this biosdevname BS is abandoned, this infection will eventually spread to other Linux distributions as well, and you won't be able to hide behind SuSE.