On Wed, 2006-10-04 at 15:06 -0500, Daniel F. de Araujo wrote: > It is my understanding that there are two "sections" of Anaconda: the > loader (written in C) and the installer (written in Python). I > understand that in order to test changes to the python portion of > Anaconda, I can simply copy my updated python modules to a floppy or to > an updates.img file and Anaconda will use my updated source code. Correct > Unfortunately, I don't understand how to exactly go about testing > changes to the Anaconda loader. Do I simply make my changes to the C > source code and follow the instructions listed on > http://lal.bizhat.com/docs/anaconda.html (steps 1-7)? If this is not > correct, could someone please layout the exact steps--or point me to > some documentation--I can follow in order to test my changes? The easiest thing to do is to do a network boot via PXE (or the equivalent if you're on another arch) with a kernel + updated initrd. anaconda/scripts/upd-initrd will let you drop in a new loader binary pretty easily and then you can boot to test stuff. Spinning an entire tree really is a bit of a last-ditch way of testing changes :) Jeremy
