Re: Kickstart ksdevice question

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



Once upon a time, Mark Haney <mark.haney@xxxxxxxxxxx> said:
> This should be easy to answer (I hope).  We routinely kickstart
> boxes to use for managing our customers RADIUS/DHCP configurations
> (along with other things).  We've had a C7 kickstart in place since
> I built one in May and are finally starting to roll it out for new
> installations.  But, I'm curious as to what ksdevice= actually does.

It just sets the NIC that the installer tries to bring up to fetch a
kickstart file from the network (and then the rest of a network install,
if you don't override it in the kickstart).

If you are PXE booting using pxelinux, add "ipappend 2" to your
pxelinux.cfg stanza and "ksdevice=bootif" to the append line.  With
that, pxelinux will add the MAC address of the PXE NIC to the kernel
command line, and the installer will pick that up and use the matching
interface for the rest of the kickstart.

-- 
Chris Adams <linux@xxxxxxxxxxx>
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
https://lists.centos.org/mailman/listinfo/centos




[Index of Archives]     [CentOS]     [CentOS Announce]     [CentOS Development]     [CentOS ARM Devel]     [CentOS Docs]     [CentOS Virtualization]     [Carrier Grade Linux]     [Linux Media]     [Asterisk]     [DCCP]     [Netdev]     [Xorg]     [Linux USB]


  Powered by Linux