I'm not sure how the anaconda order and naming NIC at this step (boot process)
between the order of loading modules or the order of PCI bus as seen by BIOS post
code?
On Thu, Nov 22, 2012 at 12:00 AM, <kickstart-list-request@xxxxxxxxxx> wrote:
---------- Forwarded message ----------
From: Jeff Wells <jwells@xxxxxxxxxxxxx>
To: Discussion list about Kickstart <kickstart-list@xxxxxxxxxx>
Cc:
Date: Wed, 21 Nov 2012 16:20:15 +0000
Subject: Re: kickstart boot option to rule the Network card name to eth0
On 11/21/12 9:53 AM, "James Cammarata" <jimi@xxxxxxxx> wrote:
>On Wed, Nov 21, 2012 at 9:25 AM, Rangsan A <rangsan.au@xxxxxxxxx> wrote:
>> Hi Kickstart Expertise,
>>
>> How can I use udev rules to manage the nic naming at the first time
>>anaconda
>> start asking for the nic that will be use for load the OS image.
>>
>> I use ksdevice=<Mac Address> at the boot option. and it is detected as
>> "eth4" while the os is install. Is there any way to rename it to
>>"eth0" ?
>>
>> For the SLES, they has kernel boot option
>> udev.rule="mac=00:1a:64:bd:13:86,name=eth0". Is there any equivalent
>>option
>> for REDHAT ?
>
>Add biosdevname=0 to your boot options and things will revert to the
>old naming scheme.
biosdevname=0 will keep the naming scheme eth* instead of em* but will not
address the NIC swapping.
_______________________________________________
Kickstart-list mailing list
Kickstart-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/kickstart-list
_______________________________________________ Kickstart-list mailing list Kickstart-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/kickstart-list
