Change from ftp.gnu.org to ftpmirror.gnu.org for GNU-sourced packages...
| Newsgroups | gmane.linux.lfs.beyond.support |
|---|---|
| Message-ID | <CAAGwWFVijsjjMbceqoUuO8bu3C6rkgz38GK+staT=sydJk=EOQ@mail.gmail.com> |
Hey guys, so I noticed an odd and seemingly random issue several times while building various BLFS packages today using the jhalfs build system. On packages sourced from GNU (ftp.gnu.org), I would occasionally get an error saying wget was "Unable to establish an SSL connection." At first I didn't think too much of it, chalked it up to normal Internet routing issues, and kept going, because the second attempt would go through with no problem. Until I attempted to build aspell (as a dependency for gedit) about 15-20 minutes ago. I tried multiple times, and just kept getting SSL connection errors. Visiting https://ftp.gnu.org using Firefox would give me about a 50/50 chance of either getting the site, or getting a "Connection timed out" error. Clearly, GNU's prime server is heavily loaded. But, when I was able to get to https://ftp.gnu.org, the page does mention that GNU provides an automated mirror selector at https://ftpmirror.gnu.org and that they would prefer users to use the mirror sites, to help reduce load on their prime server. By replacing ftp.gnu.org with ftpmirror.gnu.org in my whet commands, the files downloaded with no issue. So, I guess I just wanted to put the question out there: is there a reason that the links in the BLFS (and LFS, for that matter) books use ftp.gnu.org over ftpmirror.gnu.org? And if not, is that a change that might be worth making? Thanks, Eric Clothier -- http://lists.linuxfromscratch.org/sympa/info/blfs-support Unsubscribe: See the above information page