Description of problem: Sometimes networked installation requires a proxy. Fedora - up to 10alpha - installations let not enter a http_proxy like installer from debian or OpenSuse. How reproducible: Start Networked install behind a restrictive firewall and try access any repository from within installer. Actual results: Installation will fail 'cause nowhere (graphical nor text installer) a possibilty setting up a http and/or ftp proxy exists or nowhere the installer ask explizit for. Expected results: Such a possibility should be a base part of a modern linux installer, every other well-know distribution with own installer has something like that.
The repo editor in anaconda does allow you to add a proxy configuration to your repo, once it's failed to connect.
it should not fail to connect, it should ask in the dialogs which setting up network for a proxy. When users waited a long while before anaconda probed all variants it looks like it hangs and died. Most users will not search for a "repository editor" where it is possible to enter a proxy. Them expect a proxy configuration on its natural place: network setup. What is that complicated add after this networking question "do you want to use dhcp" a box "do you require a http or ftp proxy" dialog BEFORE waiting a long time were most users thinks anaconda died? Yes - only Geeks testing f10 alpha and rawhide. Some of them knew about this. But not users trying to install a simple stable distribution. (K/X)ubuntu asks for a proxy on networked install, OpenSuse, too I think (not real sure). Anaconda must after that prepare yum for working with proxies. This is the job of an installer. Not the job of the users.
*** Bug 468685 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of bug 125917 ***