<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
-------- Original Message --------<br>
Subject: Re: [CentOS] RHEL 6.1 beta<br>
From: Steve Clark <a class="moz-txt-link-rfc2396E" href="mailto:sclark@netwolves.com"><sclark@netwolves.com></a><br>
To: CentOS mailing list <a class="moz-txt-link-rfc2396E" href="mailto:centos@centos.org"><centos@centos.org></a><br>
Date: Tuesday, May 03, 2011 10:40:51 AM<br>
<blockquote cite="mid:4DC02203.6070002@netwolves.com" type="cite">
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
On 05/02/2011 10:47 AM, Les Mikesell wrote:
<blockquote cite="mid:4DBEC41B.5090904@gmail.com" type="cite">
<pre wrap="">On 5/2/2011 8:57 AM, Steve Clark wrote:
</pre>
<blockquote type="cite">
<pre wrap="">On 05/02/2011 09:38 AM, Lamar Owen wrote:
</pre>
<blockquote type="cite">
<pre wrap="">On Monday, May 02, 2011 06:48:37 AM Christopher Chan wrote:
</pre>
<blockquote type="cite">
<pre wrap="">biosdevname for nics...bye bye eth0!
</pre>
</blockquote>
<pre wrap="">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.
</pre>
</blockquote>
<pre wrap="">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?
</pre>
</blockquote>
<pre wrap="">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.
</pre>
</blockquote>
In my experience with Linux over the last 3 years using Centos and
RH I have never seen the ethn device<br>
numbering change, and it always corresponds to the hardware vendor
marking on the units we use. <br>
<br>
We create images and ghost them onto various hardware platforms. I
just make sure I remove the <br>
net persistent rules and the ifcfg-ethn stuff and they are then
redetected in the correct order.<br>
<br>
</blockquote>
<br>
Ditto, working with Dell hardware mostly, 2 or 4 NICs, never had an
issue with them flipping or rearranging or out of order with the
labels on CentOS5. We did have some problems with Fedora detecting
in the wrong order, though we did not experience a flip.<br>
Images made with Clonezilla work fine, though the NICs come back up
as DHCP - unsure if this was clonezilla or kudzu. Either way it was
easy enough to configure an IP manually.<br>
<br>
I can see ethX/Y, eth0/1, 0/2, etc where X is the bus and Y is the
port being acceptable, although most people probably won't
experience a benefit. The BSD method of fxp0, rl0, etc is a pain in
the rear. How exactly is the naming convention supposed to occur?<br>
<br>
</body>
</html>