<div class="gmail_quote">On Wed, Mar 23, 2011 at 23:38, Bryan J Smith <span dir="ltr"><<a href="mailto:b.j.smith@ieee.org">b.j.smith@ieee.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
From: Rajiv Gunja <<a href="mailto:opn.src.rocks@gmail.com">opn.src.rocks@gmail.com</a>><br>
<div class="im">> Summary: What you see on Linux is normal behavior for Linux,<br>
> HP-UX, AIX, Irix and Solaris.<br>
<br>
</div>Not quite.<br>
<br>
With HP-UX, HP controls the PA-RISC platform.<br>
With AIX, IBM controls the POWER platform.<br>
With Irix, SGI controls the MIPS and IA-64 platforms.<br>
With Solaris, Sun controls the Sun platforms.<br>
<br></blockquote><div><span style="color: rgb(0, 0, 153); font-family: verdana,sans-serif;">>>>> Guess you did not read what I wrote. In all the above Operating Systems, irrespective of the platform, the hardware name once assigned will not change unless you move the physical location of the network card or peripheral, on their respective bus. This is true even on convexOS and OSF/1.</span><br style="color: rgb(0, 0, 153); font-family: verdana,sans-serif;">
<br style="color: rgb(0, 0, 153); font-family: verdana,sans-serif;"><span style="color: rgb(0, 0, 153); font-family: verdana,sans-serif;">>>>> By the way, Linux distros are available on SPARC, IA-64, MIPS and POWER platforms and it behaves exactly the same way. Granted that each platform will have its own way of naming the peripheral depending the driver and kernel module.</span><br>
<br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Unfortunately for Linux, it does _not_ control the PC platform. Especially not<br>
with the legacy PC BIOS (EFI might be another story).<br>
<br></blockquote><div><span style="color: rgb(0, 0, 153); font-family: verdana,sans-serif;">>>>> What in the world does "_not_control" mean? OSes do not control the hardware. OSes are interfaces to the hardware. Kernel of each OS scans the hardware in whatever order and presents it to the OS/applications. Yes there are helpers to each platform: eeprom, bios, etc. But the underlying principle is the same.</span><br style="color: rgb(0, 0, 153); font-family: verdana,sans-serif;">
<br style="color: rgb(0, 0, 153); font-family: verdana,sans-serif;"><span style="color: rgb(0, 0, 153); font-family: verdana,sans-serif;">>>>> Same thing goes for EFI, it too is an interface for the underlying hardware. If the OS is EFI aware, then it makes use of it. Of course that seems redundant as none other than OSX seem to use it at the moment.</span><br>
<br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
So when it comes to assigning devices to names, it's not exacting by default,<br>
because of how the PC can rescan/reorder things.<br>
<br></blockquote><div><span style="color: rgb(0, 0, 153); font-family: verdana,sans-serif;">>>>> Isn't that what I said? each OS will perform a scan in a certain order and that remains constant, that is why we were able to install images on our Dell servers without having to look at each hardware to see if the OS assigned eth0 or eth2 for the first network interface. (Solaris eeprom scans the last bus first)</span> <br>
<br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Fortunately, if you set the MAC in the ifcfg-(device) files (under<br>
/etc/sysconfig/network-scripts) on a Fedora-based system, you will always get<br>
that MAC assigned to the (device). That is how it has been since around Fedora<br>
Core 4 or so. To tie down other hardware assignments, udev is utilized, such as<br>
for fixed disks.<br>
<font style="color: rgb(0, 0, 153); font-family: verdana,sans-serif;" color="#888888"><br></font></blockquote><div><span style="color: rgb(0, 0, 153); font-family: verdana,sans-serif;">>>>> I would not suggest changing mac address, unless you are sure that there will be no other machine with the same address. Plus I do not see a point to changing mac address, as it is unique to each network card manufactured around the world.</span><br>
</div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><font color="#888888">
<br>
--<br>
Bryan J Smith Professional, Technical Annoyance<br>
Linked Profile: <a href="http://www.linkedin.com/in/bjsmith" target="_blank">http://www.linkedin.com/in/bjsmith</a><br>
------------------------------------------------------<br>
LS3 Z51: When you absolutely, positively need to pass<br>
that "Smart Car" by accelerating 60-100mph in 3rd gear<br>
in around 4s so you can shift back to 6th gear and get<br>
the same 30mpg at 75mph he struggles to get at 65mph+.<br>
</font></blockquote></div><br>