On 05/02/2011 10:47 AM, Les Mikesell wrote:
On 5/2/2011 8:57 AM, Steve Clark wrote:
On 05/02/2011 09:38 AM, Lamar Owen wrote:
On Monday, May 02, 2011 06:48:37 AM Christopher Chan wrote:
biosdevname for nics...bye bye eth0!
Not by default, and according to the release notes only for certain Dell
servers ATM.
But, yes, a different way of looking at NICs is coming down the pipe. It's
about time.
EGADS Why? After working with FreeBSD for ten years it so nice not to
have to worry is this rl0, vr0, em0, fxp0, bge0, ed0,
etc in networking scripts. Why would you want to go back to that?
The numbers chosen in the eth? scheme are more or less randomized even
on identical hardware, so it is pretty much impossible to prepare a disk
to ship to a remote site and have it come up working unattended or clone
disk images for a large rollout. If this gives predictable names in
bios-detection order it will be very useful. Remote-site support is
expensive and typically not great at the quirks of Linux distributions
that you need to know to do IP assignments.
In my experience with Linux over the last 3 years using Centos and RH I have
never seen the ethn device
numbering change, and it always corresponds to the hardware vendor marking on
the units we use.
We create images and ghost them onto various hardware platforms. I just make
sure I remove the
net persistent rules and the ifcfg-ethn stuff and they are then redetected in
the correct order.
--
Stephen Clark
*NetWolves*
Sr. Software Engineer III
Phone: 813-579-3200
Fax: 813-882-0209
Email: steve.cl...@netwolves.com
http://www.netwolves.com
_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
