It is often desirable to have /tmp, /var/tmp, and other temporary file systems mounted on a "tmpfs" ramdisk rather than the actual disk, but presently this can't be setup in the anaconda installer, and /etc/fstab must still be edited post-install.
There is nothing to triage here. Switching to ASSIGNED so that developers have responsibility to do whatever they want to do with it.
Indeed, this would be nice to have. It now has to be done using firstboot. as a side note, I wish we could also tmpfs mount /var/run, but a lot of packages fail to deal with this and just assume "their" directory exist in /var/run/
This bug should be upped! I had /tmp as tmpfs in my fstab and the anaconda F15 install failed completely (until I managed to make that line ineffective) with: An error occured mounting device tmpfs as /tmp: mount failed (-2, None). This is a fatal error and the install cannot continue. Well, not mounting /tmp would have been ok too.. Also, not having /home mounted does work (/is supported). Please, this is a real bug in anaconda and not just a "FutureFeature"! Or should this be filed as a new bug? Advice welcome. @Paul: I think /var/run with tmpfs is supported now in F15..?
I see now that this is the wrong bug to report my problem. About failure of /tmp as tmpfs see bug 683434.
Implemented in the Fedora 20 timeframe.