Subject: | |
From: | |
Reply To: | Sean Slattery (Spectral Sciences Inc.) |
Date: | Fri, 10 Mar 2006 16:26:34 -0500 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
Ah! just went through that myself . . .
You have to append "ksdevice=eth0" to the kernel line in whatever boot
loader you are using.
I'm doing a netboot kickstart using the Redhat tools so my
/tftpboot/linux-install/pxelinux.cfg/default file includes:
<snip>
label 1
kernel SL42_64/vmlinuz
append initrd=SL42_64/initrd.img ramdisk_size=8192
ks=http://192.168.0.129/nodes-cfg/nodes-ks.cfg ksdevice=eth0
<snip>
Cheers,
--
Sean Slattery <[log in to unmask]>
Sr. SysAdmin
Spectral Sciences Inc.
+1 (781) 273-4775 x251
Michael Mansour wrote:
>Hi,
>
>I'm kickstarting some proliant dl360's, and as their got 2 embedded nics, each
>time they kickstart the process asks which ethernet card to kickstart from,
>eth0 or eth1.
>
>In my kickstart file I define:
>
>network --device eth0
>
>and have tried this both with the "--bootproto dhcp" line and with assigning
>IP address lines, both methods ask which ethernet card to use.
>
>I'm kickstarting SL42 machines.
>
>Does anyone know how I tell kickstart to always use eth0?
>
>Thanks.
>
>Michael.
>
>
--
Sean Slattery <[log in to unmask]>
Sr. SysAdmin
Spectral Sciences Inc.
+1 (781) 273-4775 x251
|
|
|