On Sun, 18 Apr 2021 at 10:51, Philip Paeps <phi...@freebsd.org> wrote:
> > > It looks like there were at least experiments with pointing > freebsd-update at AWS, similar to how portsnap currently works. I will > check if these experiments went anywhere and possibly point > freebsd-update there instead. > The AWS freebsd-update has been working fine for quite a while. All project mirrors are slow in Australia so we have been using the AWS one since Colin brought it online to make it a better experience for our team to update the fleet. FWIW adjust update.FreeBSD.org to aws.update.FreeBSD.org in /etc/freebsd-update.conf and you are good to go. Can the project look at offering traditional mirrors for base and pkgs rather than the current offering? Those that want to stand up un-official mirrors can do so by pointing rsync to a Tier 2 mirror for updating purposes so they can provide faster, localised access. From Melbourne to our closest geo mirror is 240ms, this latency really drags out updates, so having a mirror out of a Melbourne DC would be beneficial. Cheers, Jason. _______________________________________________ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
