[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Let's talk about some F9 (and beyond) features for anaconda

Title: Signature
Alexander Todorov wrote:
Hello list,
better late than never, here it goes:
feat: Configure yum .repo file based on installation source.

After installation the only .repo files that are present are the one installed by rpm packages. They point to official Fedora servers for getting a mirror list. They are no helpful is installation is from unofficial mirror or a local one (e.g. LAN).
In contrast when performing network installation with Debian, one is asked to choose a mirror and that's saved in /etc/apt/source.list
This feature will save the time for configuring a .repo file after installation.

For http and ftp installs just take the list of configured repositories and dump it into a .repo file.
CDROM/DVD/hard drive install - N/A
NFS -N/A or some clever way to mount the NFS share, probably automount.
I would say N/A for NFS since http/ftp is the majority of installation protocols used I believe.

Q: Is there a substantial difference in handling http unified and split trees ?

Any thoughts are welcome.


Anaconda-devel-list mailing list
Anaconda-devel-list redhat com
This would be nice if it allowed the specification of NFS based yum repositories that are used during the install (especially kickstart) and then saved these either as a replacement for or in addition to the "standard" ones. Currently all of my kickstart scripts have to use a merged local and Everything repository for build and the update after reboot as we provide all of our data via NFS! We overwrite the yum.repos.d directory with a local copy which points to rsynced structures for the release.



Howard Wilkinson



Coherent Technology Limited



23 Northampton Square,



United Kingdom, EC1V 0HL


howard cohtech com


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]