On 2010-03-24 14:20, Philippe Eveque wrote: > Hi > > > May be the following commands might help a little. Not sure > > > [r...@sys]# cobbler system dumpvars --name=<yoursystem> > [r...@sys]# cobbler profile dumpvars --name=<profileAssigned2yoursystem> > > But no sure we will understand what happened at deployment time though. > > > Phil. OK, so now I've had the chance to try some more.
If I explicitly point out the systems very own ks-file at kickstart time, this of course works as expected. However, there must have been a change between 1.6 and 2.0 since before upgrading I was able to get this to work with a generic ks-file that was at ks-time updated to reflect the systems own parameters. Either that or I'm doing something very wrong, and have been all along using 1.6. This workaround (as I see it) is a bit annoying but workable. Isn't there a way for me to use a more generic ks-file using 2.0, and still get system specific options set? If not, doesn't that completely remove the need for any other ks-files than those that are system specific? /Jonas _______________________________________________ cobbler mailing list [email protected] https://fedorahosted.org/mailman/listinfo/cobbler
