On Tue, 2003-09-23 at 10:42, Jeremy Katz wrote: > There are a few howtos out there for creating all new CD sets, but if > you're really wanting to test changes, that's not the easiest way to do > so. > > The easiest thing to do is to use an updates.img to test your changes. > Just make an ext2 floppy and copy the python files which you're making > changes in to it. If you're doing a CD install, boot with 'linux > updates' and provide the floppy when prompted. If you're doing a > network install, it's even easier. Just drop an image of the > updates.img (or you can just start with loopback mounting an empty > ext2fs, which is what I usually do) in the RedHat/base/ directory and it > will get loaded and used. Pardon my ignorance, but I don't understand some of the things you said even after a fair amount of searching. I've narrowed it down to mostly yes-or-no or which-of-these-two-cases questions, so hopefully it shouldn't be hard to answer my long list of questions. :) What I've done: I don't have a floppy drive but I still want to be lazy (i.e. use the way you called the easiest, namely a network install), so I went and set up and ran an nfs installation without any changes to make sure that I understood it and that I could get it to work. I then starting googling on updates.img and anaconda, and subsequent stuff I found such as mkcramfs. My questions: Is the updates.img just a file created by mkcramfs? (If not, how is it created?) What should the directory structure of the updates.img filesystem be--just a bunch of python files in /, or should they be in a more well defined place such as /usr/lib/anaconda? What did you mean by "you can just start with loopback mounting an empty ext2fs"? My guess was that perhaps you mean mounting a loopback filesystem as read-write (is that even possible?) so that you could easily add several files, but I'm not really sure. The nfs mounted directory from which I installed merely contains the iso images for the first three CDs. So do I simply create a RedHat/base/ directory inside the directory that contains these isos and then stuff the updates.img file there, or will I need to make a full tree from the contents of the isos manually? > And if you have changes, the best way to ensure they don't get lost is > to put them in bugzilla. Sending them here as well doesn't hurt, > because then there can be discussion around them, but posts to a mailing > list are easy for me to forget; if I forget about things in bugzilla, it > stays there in my face as a constant reminder ;) Will do...that is, so long as I can verify that any patches I create actually work--at least for me. :) Thanks, Elijah
