Hide Forgot
Description of problem: At least twice that I know of (maybe others) biosdevname updates have changed the "immutable" names assigned to ethernet devices, see: http://home.comcast.net/~tomhorsley/game/biosdevname.html If biosdevname were simply used to select the initial names for new interfaces, but the 70-persistent-net.rules file was still generated and still obeyed, then these changes to the immutable naming would not screw up existing systems. Version-Release number of selected component (if applicable): general problem, not version specific How reproducible: Every so often it happens on an update. Steps to Reproduce: 1.See above 2. 3. Actual results: Immutable names change Expected results: No name changes. Additional info: Just think about it for a minute please: Every new quirky motherboard or PCI extender or wot-not that gets produced is likely to introduce some new twist that biosdevname needs to deal with. Whatever change is made for this new quirk is quite likely to interact in some totally unpredictable fashion with the millions of quirky motherboards already out there. You can't possibly test on every one of them to find out if the change is going to jerk the rug out from somebody else. Putting back the persistent rules will eradicate all these problems. Pretty please?
Hi Joachim, It would be great if you could test the biosdevname package from https://bugzilla.redhat.com/show_bug.cgi?id=816536#c28 and let us know if it addresses the issue reported in the thread - http://lists.fedoraproject.org/pipermail/test/2012-May/107811.html
(In reply to comment #1) > Hi Joachim, > > It would be great if you could test the biosdevname package from > https://bugzilla.redhat.com/show_bug.cgi?id=816536#c28 ******************************************************* I'm sorry, but I did not find any rpm to download. Please tell me the download location :-) ******************************************************* > > and let us know if it addresses the issue reported in the thread - > http://lists.fedoraproject.org/pipermail/test/2012-May/107811.html
Joachim, It is a tarball source, you will have to build the source for biosdevname on your system to test.
(In reply to comment #3) > Joachim, > > It is a tarball source, you will have to build the source for biosdevname > on your system to test. Good news: after building the tarball, the new biosdevname renames em15 to em1 (as previously) when rebooting. I think, this solved my issue. Thank you, guys!
biosdevname-0.4.1-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/biosdevname-0.4.1-1.fc17
Package biosdevname-0.4.1-1.fc17: * should fix your issue, * was pushed to the Fedora 17 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing biosdevname-0.4.1-1.fc17' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-10778/biosdevname-0.4.1-1.fc17 then log in and leave karma (feedback).
biosdevname-0.4.1-1.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.