<div class="gmail_quote">On Thu, May 7, 2009 at 3:28 PM, Doug Chapman <<a href="mailto:doug.chapman@hp.com">doug.chapman@hp.com</a>> wrote: <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> I came up with what I think is a better way to fix the iso booting issue. I wrote a little script that takes an existing boot.iso image and pulls out what we don't care about. This prevents us from needing to make kernel config changes and also prevents us from needing to modify the anaconda tools. I don't consider this a long term fix but it does the job for now. I raised the issue with the anaconda guys since they are likely to run into this on x86 efi systems soon. Currently the initrd.img for x86 efi systems isn't as big but it seems to grow each release so I imagine for F12 they will hit this also. To use this just grab the existing boot.iso and run: # shrinkiso.sh boot.iso This will generate a new file called newboot.iso that should boot. The one thing missing is this script doesn't implant the MD5 checksum so verifying the media during the install will fail. Dave, perhaps you can generate a fixed iso and post it on the site. thanks, - Doug </blockquote><div> I uploaded both the original boot.iso and the newboot.iso from your script. I also ran the tool to put the md5sum in the iso so media check should work OK now. The latest build appears to install cleanly! Currently both the development and development-lastgood trees are identical so choose either one (although by the time you read this I may have uploaded a new experimental tree to the devlopment dir so probably best to grab from development-lastgood). You can grab this from: <a href="http://www.linuxdudes.org/cowboyboot/">http://www.linuxdudes.org/cowboyboot/</a> </div></div> Dave