If you opt out of fastestmirror, it just randomly picks a host from the mirrorlist gotten from the metalink server, if you wonder what I mean, you can load the metalink url from one of the /etc//*.repo files into Firefox for example for updates (have to replace the $releasever with '38' and $basearch with 'x86_64' )Ĭode: lrwx. The dnf command saves off the fastest host ping results in a file called /var/cache/dnf/fastestmirror.cache, I'm not sure how often it retries the pings but it doesn't do them every time (if it did, why have a file?)

If it's not, the root run might have run against a different fastest host then your personal user. It's pretty likely the fastest one for the first set will be the fastest one for the 2nd run but it's possible it won't be. Imagine pinging a few dozen hosts, then waiting a few minutes and pinging them again. PS: After I set fastestmirror to true, both 'dnf repoinfo' and 'sudo dnf repoinfo' now show the same package sourcesI'm not saying fastestmirror WILL make the sources different, just that it could possibly happen.

Google Chrome 117.0.5938.132 instal