On Wed, 2013-11-27 at 18:01 +0800, Kun Huang wrote: > I'm facing an awkward problem now. As we know, kickstart is design to > config new system and some shell scripts may be wrote in %pre or %post > section. So for a relatively complex system, kickstart file would > contain many lines of shell script. And for my system, totally 300 > lines in my kickstart files. Unfortunately, one guy in my team has to > update this kickstart file for complicated network setting and he > hates finding his codes in such 300 lines. And he wants to move his > script into another place, like stage2.img. But it seems not > reasonable because his advice will let me rebuild stage2.img for any > tiny changes in script. That's a waste of time. But as the same time, > we can't use "include" command instead because I have to set kickstart > file in boot options, which is a place can't accept multiple files. > Finally, are there some tricks in kickstart structure could split some > scripts out? You can have a single kickstart file specified in the boot options and include the other files from there. If you have the other files available in the installation environment, it shouldn't be a problem. And if you want to fetch kickstart file(s) over network and don't have them available in the installation environment, you could use a trick of having the ks URL pointing to a CGI script generating the kickstart file. When combined with the 'kssendmac' boot option it can even provide different kickstarts for different machines. -- Vratislav Podzimek Anaconda Rider | Red Hat, Inc. | Brno - Czech Republic _______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/anaconda-devel-list
