On Fri, Feb 20, 2009 at 2:28 PM, Ruben Kerkhof <[email protected]>wrote:
> Hi Michael, > > On Feb 20, 2009, at 4:22 PM, Michael DeHaan wrote: > > > I presume this means you also have a static configuration (otherwise > > ksdevice=bootif would be fine for you). > > Exactly, for one reason or the other there's no dhcp and pxe allowed > on our network. > > > I'm not sure I want such a specific setting in a cobbler system if it > > would only work for buildiso, as that would be a bit hard to explain. > > > > Perhaps we could make buildiso more template based to give you > > something > > that would allow use of --ksmeta to provide arbitrary variable usage. > > > > --Michael > > With the latest patches that went into 1.4.2 all is working fine for > us with a static config, except we're using eth2 as ksdevice. > I've already set ksdevice=eth2 in /etc/cobbler/settings, maybe that's > something which can be used in action_buildiso, otherwise a template > would be great. > > Thanks for the help, > > Ruben > Ruben- Have a look at http://fedoraproject.org/wiki/Anaconda/Options, the section about ksdevice, you can set ksdevice=link. ksdevice Takes one of 4 types of argument which tells install what network device to use for kickstart from network: - An argument like 'eth0' naming a specific interface - An argument like 00:12:34:56:78:9a indicating the MAC address of a specific interface - The keyword 'link' indicating that the first interface with link up - The keyword 'bootif' indicating that the MAC address indicated by the BOOTIF command line option will be used to locate the boot interface. BOOTIF is automagically supplied by pxelinux when you include the option 'IPAPPEND 2' in your pxelinux.cfg file
_______________________________________________ cobbler mailing list [email protected] https://fedorahosted.org/mailman/listinfo/cobbler
