Tom Brown wrote:
Jeff Schroeder wrote:
On Wed, May 6, 2009 at 10:16 AM, Tom Brown tom@ng23.net wrote:
Is it possible to have cobbler not blat pxelinux.cfg but merely add to it or delete from it?
We have a situation where the same build box is needed to PXE different systems, jumpstart etc, but i dont want to not be able to use cobbler. Anything that gets added into there not by cobbler gets removed when a sync is run.
Any ideas on if this could work?
The pxelinux.cfg is generated from a template. I believe it is /etc/cobbler/pxe/pxedefault.template. You should be able to add what you want to the template and have it generate the file. You could also use host specific pxe config files for the solaris boxes or whatnot.
moved to user list at Michael's request
I see that pxedefault.cfg contains
DEFAULT menu PROMPT 0 MENU TITLE Cobbler | http://cobbler.et.redhat.com TIMEOUT 200 TOTALTIMEOUT 6000 ONTIMEOUT local
LABEL local MENU LABEL (local) MENU DEFAULT LOCALBOOT 0
$pxe_menu_items
MENU end
That is the pxe menu configuration isn't it ? Its possible i am getting confused but what i need to happen is that files within /tftpboot/pxelinux.cfg/ are not removed if cobbler does not know about them. If thats possible by using that template could you give any tips as what to put in there?
sorry - OK really sent to user list now
Tom Brown wrote:
Tom Brown wrote:
Jeff Schroeder wrote:
On Wed, May 6, 2009 at 10:16 AM, Tom Brown tom@ng23.net wrote:
Is it possible to have cobbler not blat pxelinux.cfg but merely add to it or delete from it?
We have a situation where the same build box is needed to PXE different systems, jumpstart etc, but i dont want to not be able to use cobbler. Anything that gets added into there not by cobbler gets removed when a sync is run.
Any ideas on if this could work?
The pxelinux.cfg is generated from a template. I believe it is /etc/cobbler/pxe/pxedefault.template. You should be able to add what you want to the template and have it generate the file. You could also use host specific pxe config files for the solaris boxes or whatnot.
moved to user list at Michael's request
I see that pxedefault.cfg contains
DEFAULT menu PROMPT 0 MENU TITLE Cobbler | http://cobbler.et.redhat.com TIMEOUT 200 TOTALTIMEOUT 6000 ONTIMEOUT local
LABEL local MENU LABEL (local) MENU DEFAULT LOCALBOOT 0
$pxe_menu_items
MENU end
That is the pxe menu configuration isn't it ? Its possible i am getting confused but what i need to happen is that files within /tftpboot/pxelinux.cfg/ are not removed if cobbler does not know about them. If thats possible by using that template could you give any tips as what to put in there?
sorry - OK really sent to user list now
This is the template for the defaults file, yes, which covers what happens when any system without a specific IP or MAC binding to a particular profile will get.
You can put in anything you like, either before the $pxe_menu_items or after. Cobbler will insert what it thinks should be there at that point.
--Michael
cobbler mailing list cobbler@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler
This is the template for the defaults file, yes, which covers what happens when any system without a specific IP or MAC binding to a particular profile will get.
You can put in anything you like, either before the $pxe_menu_items or after. Cobbler will insert what it thinks should be there at that point.
thanks - that makes sense, this will allow me to add non cobbler managed systems to the pxe menu correct?
Is it possible though that i can somehow just add files to the pxelinux.cfg directory (as this is what currently happens) but have cobbler not remove them? Why does cobbler completely remove stuff from the pxelinux.cfg directory that it knows nothing about?
i ask this as we would need to pxe many systems and without human intervention so the menu option is not really viable but alas neither is adding them to cobbler as they are not linux systems
i am not sure if i am making sense if not just say and i will try to explain better
thanks
Tom Brown wrote:
This is the template for the defaults file, yes, which covers what happens when any system without a specific IP or MAC binding to a particular profile will get.
You can put in anything you like, either before the $pxe_menu_items or after. Cobbler will insert what it thinks should be there at that point.
thanks - that makes sense, this will allow me to add non cobbler managed systems to the pxe menu correct?
Yes.
Is it possible though that i can somehow just add files to the pxelinux.cfg directory (as this is what currently happens) but have cobbler not remove them? Why does cobbler completely remove stuff from the pxelinux.cfg directory that it knows nothing about?
Not really, no.
i ask this as we would need to pxe many systems and without human intervention so the menu option is not really viable but alas neither is adding them to cobbler as they are not linux systems
You could set them up in DHCP to use a different next-server, possibly.
i am not sure if i am making sense if not just say and i will try to explain better
thanks _______________________________________________ cobbler mailing list cobbler@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler
cobbler@lists.fedorahosted.org