Robert P. J. Day wrote:
On Sun, 13 Jan 2008, John Summerfield wrote:man ifrename man ifrename man ifrenamesorry, what was that again? :-)
I have no idea of how that happened, I saw it flash up as seamonkey was sending.
Robert P. J. Day wrote:i apologize for rambling on so much this morning ... argh. i'm not
Don't get too apologetic, this is way more interesting than emails from people who can't figure out how to use their MP3 players, or read replies from those who would help them.
sure this was the right solution but, based on what you can see in my earlier posts, the broadcom wireless chip seemed absolutely determined to grab control of both wlan0 and eth0. so i just gave up on eth0, and created /etc/sysconfig/networking/devices/ifcfg-eth1, and added "alias eth1 sky2" to /etc/modprobe.conf, rebooted, ran s-c-n, where, under "Hardware", i can now see an entry for the Marvell Fast Ethernet Controller associated with eth1, and i can activate that interface. should i have known that? is it normal behaviour for the b43 driver to also grab eth0? that's certainly not what i've seen on some of my other systems. is this a bug? in any event, i'm not convinced this is actually the *proper* fix, it's just *a* fix. i need a drink.Rebooting is the easy way to get HAL or whatever to scan the PCI bus and load drivers. Probably, starting whatever in /etc/init.d would have done as well, but rebooting is orderly and supposedly repeatable and most likely to be correct. Once the drivers are loaded, "ifconfig -a" identifies the devices' names that they have chosen. I suspect that when drives are being enumerated asynchronously, the names they actually get might be a little random, especially when there are two or more identical drives (think two PCI network cards with the same realtek chips). Note too, that these days it's possible for users (eg RPD) to rename devices.ok, i'll definitely give that a shot, but i'm still curious as to why the wireless interface insists on grabbing *both* eth0 and wlan0 on that system when, on another system of mine, eth0 is assigned to the onboard intel ethernet controller, while the wireless interface is content with just wlan0. somehow, the first result just seems wrong.
An important point about ifrename is that whatever RPD can do with it, the folk who maintain the scripts can do too, and I'm sure they do.
find /etc -type f -print0 | xargs -0 grep -l ifrenameI don't really want to enter into why your system behaves so oddly, it's outside my experience and I don't have the same hardware, and I've long suspected the right hardware is key. That and timing.
I presume this is a test system? It would be interesting to script (kickstart + %post) the install to get to a repeatable state, freshly installed and the network configuration deleted.
Do run these commands as root: updatedb locate /ifcfg- I have seen multiple copies of network configuration data. -- Cheers John -- spambait 1aaaaaaa coco merseine nu Z1aaaaaaa coco merseine nu -- Advice http://webfoot.com/advice/email.top.php http://www.catb.org/~esr/faqs/smart-questions.html http://support.microsoft.com/kb/555375 You cannot reply off-list:-)