Alan, For point 2, I'm feeling an echo of 'Support custom boot loader configuration file templates' ( https://github.com/cobbler/cobbler/issues/1328).
Part of the conversation there was: do these pieces of pxe menu need to be associated with a distro or with an image? Can we create a sufficiently useful abstraction that serves both use cases? -- Jess On Mon, Nov 10, 2014 at 7:18 AM, Alan Evangelista <ala...@linux.vnet.ibm.com > wrote: > On 10/24/2014 03:27 PM, Jörgen Maas wrote: > >> A user contributed this: https://github.com/cobbler/ >> cobbler/wiki/Microsoft%20systems%20center >> >> > Thank you, Jörgen. According to docs, the steps are extract some PXE > related files from SSCM boot media, > copy them to Cobbler server and setup xinet conf file and boot loader conf > file. Note that doc suggests that > pxedefault.template should be updated manually, so this would break Linux > installations on the same Cobbler > server. Also, adding a distro and cobbler sync currently requires that > each distro has an initrd value, which is > not set here. Thus, there is no "Windows installation" feature; doc above > simply teachs how to hack Cobbler > and reuse its automatic DHCP/boot loader conf file generation to support > Windows installation. > > imho either "windows" should be removed from breed list or Windows > installation should be correctly supported > in Cobbler. This means (1) allowing creation/sync'ing of a distro without > initrd, (2) add a Windows SSCM boot > loader conf file template, (3) make tftpgen.py use this template when > windows breed is selected, (4) improve > documentation about Windows installation. > > > > Regards, > Alan Evangelista > > _______________________________________________ > cobbler-devel mailing list > cobbler-devel@lists.fedorahosted.org > https://lists.fedorahosted.org/mailman/listinfo/cobbler-devel >
_______________________________________________ cobbler-devel mailing list cobbler-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/cobbler-devel
