Erik, I assume that one can pick and choose which members of the anaconda kickstart class to modify and those that aren't redefined in the %installclass are left to utilize the original anaconda kickstart class routines? I'm fairly comfortable with python; this is a very interesting way to add some nice features to our build process. It would be very cool if you could possibly give a quick little hello world example of how to make use of %installclass. Thanks for your help, Mike Erik Troan (ewt@xxxxxxxxxx) said: > On Mon, 10 Sep 2001 Rebecca.R.Hepper@xxxxxxxxxxx wrote: > > > Is it possible to alter the ks.cfg file on the fly in RedHat 7.1? > > No, but you can write a custom anaconda install class that does exactly > this. This isn't easy to do, so if you don't know python don't try. > > If you do know python, you can put a %installclass section at the end of your > kickstart file and define a new kickstart class that overrides the default > one. That class will be used to parse the kickstart file rather then the > default class. > > You can use this with 7.1 to do almost anything. It didn't exist in 7.0, and > I don't know if it's in the new beta releases. Anaconda had some major > surgery for the betas, and this feature may have been dropped as it > seems too complicated to actually use. > > Erik > > ------------------------------------------------------------------------------- > | "Who is John Galt?" - Atlas Shrugged by Ayn Rand | > | | > | Linux Application Development -- http://people.redhat.com/johnsonm/lad | > > > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list@xxxxxxxxxx > https://listman.redhat.com/mailman/listinfo/kickstart-list
