Description of problem:
I just installed Debian, and noticed that the mirror I selected as a HTTP
install source became my default updates mirror.
I still have to configure this manually in Fedora
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. PXE boot into a HTTP install
2. Enter a local HTTP mirror
3. Finish install, run 'yum update'
Update from main, busy, expensive fedora mirror
Update from local, cheap fedora mirror used for the install
Debian does this very nicely. Perhaps the install mirror should just be the
first choice, falling back to the others if unavailable or apparently stale (if
it only had the install tree, for example).
Adding FutureFeature keyword to RFE's.
I think this RFE is mostly obsoleted by our use of the Fedora mirror manager system these days. You should get the fastest (probably most local, though not guaranteed) mirror when you do an installation, and this behavior should carry over to the installed system. Of course this might not be the same mirror as what's the fastest could change over time.
I agree that one important use case has been solved by the mirror manager, but this does not address in-network mirrors very well.
This will not address private mirrors which are not managed by mirror manager or locations where those are not connected to the Internet.
Could anaconda check the updates path automatically? i.e. search for "releases" and replace with updates/$releasever/$basearch?
so, if PXE install used repo=http://repo/pub/fedora/linux/releases/14/Fedora/i386/os then decipher the base URL (http://repo/pub/fedora/linux) and try to access updates and if possible releases/14/Everything.
At the college where I work we currently run Fedora as the distro of choice and can have up to 60+ clients needing the local repo. In this case not having to break the default to make installation and updates work would IMO be a boon. We feel it beneficial to keep the installation and user experience as standard as possible.