From Bugzilla Helper: User-Agent: Mozilla/4.0 (compatible; MSIE 5.22; Mac_PowerPC) Description of problem: When doing a network install of Fedora, you are prompted to fill in the FTP server and directory for the source files. This makes sense, and you should still have the ability to do this, but it would be nice if there were one or two generic install locations available to select with a checkbox or drop down box for those of us who just want to install from the generic RH servers (or a few suitable mirrors). Generally the URL to the source files is quite long, when downloading from a mirror, ie: Server: ftp.dulug.duke.edu Path: ftp.redhat.com/pub/redhat/linux/beta/severn/en/os/i386/ For a newbie, it can be daunting to find a server that hosts the i386 directory, and then type in a huge URL, without making a mistake somewhere along the way and giving up. I think of it kind of like Anaconda's option for selecting a NTP server. You can manually type in any server you want, but for those of us not wanting to go look up a suitable NTP server, we can just select clock.redhat.com from a list, and be off to the races. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1.Choose FTP (or other network) install 2. 3. Actual Results: Have to find an FTP server URL on ANOTHER computer, since the computer running anaconda is in the process of loading the OS Expected Results: Have a drop down box to choose a pre-configured FTP install location Additional info:
To do this nicely really requires a sane mirror list (see my post to fedora-devel-list I think from over the weekend). Mirrors are all organized differently, so you can't just assume any one layout :/
You are CERTAINLY correct on the layout of the mirrors, but worst case scenario, you could just use RH server information, which is fairly consistent (same as you do with the NTP server information in anaconda).
At least from my country, access to RH servers is much (much as in a few orders of magnitude) slower then to local metropolitan mirrors. With a fiber optic metropolitan connection, but only 64/128 kbps international access you will definitely prefer manually typing the path to the local mirror rather then wait for ages. In my case, I already know by heart 3 major local mirrors and just randomly switch among them when I need to download. The difference is 6 MB/sec (local mirrors) versus 3 kb/sec (RH servers). Not to mention that, since I have a lot of systems to take care of, I have a local (local as 'placed in my company') mirror of the distributions I currently use, which is rsync-ed with an official mirror, and periodically has the updates included in the installation tree, so as to avoid applying them after each new install.
*** This bug has been marked as a duplicate of 35236 ***
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.