1. Start the installation with dd=http://path/to/vfat-dd.img vfat-dd.img being a VFAT driver disk 2. Error out with "Invalid argument" The current HEAD code tries to mount loopback images as vfat in mountLoopback(), but the RHEL3 code doesn't. HEAD: /* FIXME: really, mountLoopback() should take a list of "valid" * filesystems for the specific type of image being mounted */ if (doPwMount(filename, mntpoint, "iso9660", IMOUNT_RDONLY, NULL)) { if (doPwMount(filename, mntpoint, "ext2", IMOUNT_RDONLY, NULL)) { if (doPwMount(filename, mntpoint, "cramfs", IMOUNT_RDONLY, NULL)) { if (doPwMount(filename, mntpoint, "vfat", IMOUNT_RDONLY, NULL)) { RHEL3: if (doPwMount(filename, mntpoint, "iso9660", 1, 0, NULL, NULL, 0)) { if (doPwMount(filename, mntpoint, "ext2", 1, 0, NULL, NULL, 0)) { if (doPwMount(filename, mntpoint, "cramfs", 1, 0, NULL, NULL, 0)) { logMessage("failed to mount loop: %s", strerror(errno)); Patch attached.
Created attachment 126537 [details] anaconda-try-vfat-for-dd.patch
Note that having the image on a local device such as a floppy instead will mount the floppy as vfat successfully.
This issue is on Red Hat Engineering's list of planned work items for the upcoming Red Hat Enterprise Linux 3.8 release. Engineering resources have been assigned and barring unforeseen circumstances, Red Hat intends to include this item in the 3.8 release.
Adding blocker bug 185486 and IBM group per request by John Jarvis.
Mistakenly added to IBM group, removing.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHEA-2006-0443.html