Yep, same here.Remote configuration from a ks / network install server, escpecially for MS boxes looking to migrate to linux or dual boot. The ks file would then be delivered via CGI to the network installation.
We have a simple cgi that does this now. We have stubs of files that are
matched with 'types' of systems.
then the types are matched to hostnames.Yes I understand - see original post - there are several CGI projects out there that generate the ks file more or less
automatically. Thats the Output backend if you will, however I need the user input _frontend_ for customized installations on various types
of machines. For that Ive got to have the detail that s-c-kickstart provides. And yes Ive also seen the nice PHP frontend you guys did a while back. But as I said above that amounts to fork.
Yep same here, all PXE.so the kickstarting host points at the cgi, the cgi looks at the hostname, matches it to the system 'type' then assembles the full ks.cfg from the stubs and hands it back to the requesting system.
works nicely and means no messing about with ks.cfg or removable media (we do all installs via pxe)
-sv