Michal Jaegermann wrote:
On Sun, Jan 04, 2009 at 08:56:10PM +0900, John Summerfield wrote:
Michal Jaegermann wrote:
On Sat, Jan 03, 2009 at 05:03:24PM +0900, John Summerfield wrote:
You misunderstood me. The wireless came up as eth0.
And? Something enumerated it first. If you dislike it then edit that
in /etc/udev/rules.d/70-persistent-net.rules. A comment there says
"# You can modify it, as long as you keep each rule on a single line".
"no geek required."
"No geek needed". Following your criteria only a geek would care
what specific names were stuck to network interfaces. Again - why
do you care? If you do you are free to adjust things to your taste.
Michal
Evidently you haven't had your system mucked up by a kernel upgrade. "no
geek required" does not mean "no geek allowed," and I do still need to
care about these things. Renaming network interfaces at random can lead
to difficulties administering a system remotely.
Whether I care about their names or not, I do care that the cable
plugged into _that_ socket goes to my ADSL modem, the next one goes to
the staff network and the third to the student network.
If a kernel upgrade changes the first NIC's configuration from "no IP"
to "student LAN IP," I have to be on site to sort it out. That's what
renaming interfaces can do.
--
Cheers
John
-- spambait
1aaaaaaa@xxxxxxxxxxxxxxxx Z1aaaaaaa@xxxxxxxxxxxxxxxx
-- 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:-)
--
fedora-test-list mailing list
fedora-test-list@xxxxxxxxxx
To unsubscribe:
https://www.redhat.com/mailman/listinfo/fedora-test-list
