On Fri, Mar 02, 2007 at 20:44:57 -0500, Chris Lumens <clumens@xxxxxxxxxx> wrote: > > No, there most likely won't be. However if you've got a CVS checkout, > why don't you just toss the updated raid.py into an ext2 filesystem > image, put that up on a website, and use updates= on the boot > parameters? You don't need to go through the full pain of making an > updated boot.iso. I got this to work (at least as far as getting anaconda to run). I bugzilla'd the problem with getting it to work with a floppy. I was able to burn a DVD and get it to work though. I have two DVD drives and don't know how well this would have worked with just one. As an RFE that probably won't get done, it would have been nice to have been able to get the updates off the DVD I was using for the install. Unlike for the network install, it doesn't grab images/updates.img, but rather all of the DVD. This doesn't work so well, as the install DVD had more data on it than I have memory. This is a rare enough case, that it probably isn't worth the effort to do. If it had been a bad rpm I would have replaced the bad rpm on the DVD, it is only because it was an anaconda file that was corrupt that I needed to use the updates system. And I am also in the odd situation of burning my own spins, so that I can get the anaconda changes on to the install DVD. -- fedora-test-list mailing list fedora-test-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list