The new device naming convention aka eth0 is now p2p1

You may or may not have run into this yet. I’ve only seen it a few times and while I understand the reasoning behind it, it plays hell with kickstart (since you have to know the interface name and assume it’s eth0). The behavior can be disabled, apparently through a boot parameter:

biosdevname=0

I’ll test it when I run across a machine that does this to see if it can be handled gracefully in kickstart.

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s