Re: Unexpected NIC naming f23 firewall implications

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 





Am 08.11.2015 um 22:59 schrieb Björn Persson:
Reindl Harald <h.reindl@xxxxxxxxxxxxx> wrote:
a skilled sysadmin can solve all that problems at his own, a non-skilled
has repeatly problems to solve which did not exist in the past where
eth0 was normal

I guess you were lucky in the past. My experience was that interface
names were unstable in the "eth0" days. After an upgrade eth0 and eth1
could suddenly swap names with each other, and adding or removing a
network card could trigger a renaming of other network cards that had
not been touched. Network interface names have always been unreliable,
and apparently they're still unreliable, unless you have configured
your own names and ensured that your configuration overrides anything
else that tries to rename interfaces

what about read and quote correctly?

"doing that on systems with just one ethernet interface (the majority) every few years is nothing else than asking for troubles"

the problems you are talking about *did not* affect single-nic machines, the new ones does

Attachment: signature.asc
Description: OpenPGP digital signature

-- 
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux