On 5/19/2015 12:54 PM, m.roth@xxxxxxxxx wrote: > Excerpt I *still* see absolutely no use in an enterprise environment, where > we're *all* wired, even the laptops when folks bring them in. This improves > throughput and security, of course. >> Great post. I am just in the process of building my first CentOS 7 host >> and was wondering whether to use NetworkManager. You've swayed me. I've >> always disabled it on CentOS 6. Your point about these new funky device >> names is really good. I will miss my simple eth0 and eth1 but tech moves >> on. > And that one drives me nuts. It breaks PXE boot kickstart builds. Maybe > *you* have all same model systems from the same manufacturer; we've got > boxen from...<thinking> at least five or six manufacturers, of varying > ages, from the 10+ yr old Altix 3000 from SGI, to the current one from > SGI, to my 5 yr old Dell workstation, to some old Penguins and several > Suns (soon to set, the sooner the better...). How do you deal with > everything from em1 to ens3f0, which comes up *only* after you start to > install.... In what conceivable way is this better than having your > scripts know that eth0 (or even em1) is always going to be how to talk to > the world? > <snip> > > mark "they sound like ham call letters" > > _______________________________________________ > CentOS mailing list > CentOS@xxxxxxxxxx > http://lists.centos.org/mailman/listinfo/centos > We have licensed software, using flexlm, whifh chokes and pukes, unless it is able to communicate on eth0, so I have to jump through hoops to ensure the correct interface IS eth0. Until they fix this issue, I have no choice. -chuck --
_______________________________________________ CentOS mailing list CentOS@xxxxxxxxxx http://lists.centos.org/mailman/listinfo/centos
