On 5/19/2013 7:58 AM, Hans Witvliet wrote:
For new installations one name is as good as another. I personally find new names more useful. If you want to disable them, it is trivial. You'll get whatever kernel gives you.
Installations are only new once. When you have a a short obsolescence schedule as found in OpenSuse, you have to upgrade in place more often than you fresh install. The big surprise of having interface names wander around or switch positions (like they did in one of the OS 10.x releases) can be pretty time consuming to sort out. Most of us that encountered this went back an imposed the old interface names because there were just too many things that were dependent on those names. Firewalls, Samba, cups, and various other daemons were all hard coded for those names back then. (and still today in some cases). True, anyone using OpenSuse has volunteered to be a lab rat, and anyone relying on it for any critical business should be using SLED or SLES. But it didn't always use to be that way, and some of us have been using some form of Suse long enough to remember those days. I find zero benefit in any new naming convention for interfaces. It was great when you could build a machine, grab your permanent marker and write ETH0 on the back of one nic and ETH1 on the other, and never expect to have to change that for the life of the hardware. I was livid when an OS upgrade (somewhere after OS 9.3) decided to swap the order of nics and exposed an entire samba server to the wide wooly world. -- _____________________________________ ---This space for rent--- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org