E-mail sent to www@gentoo.org by Walter Dnes: """ The sequence of steps given in... http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?full=1#book_part1_chap6 appears to be causing problems, according to traffic on the Gentoo users mailing list. Here is my diagnosis of what is going wrong. The current sequence in Chapter 6a is... - first run mirrorselect - then chroot The current LiveCD appears to have IPV6 networking enabled. Paradoxically, it is causing problems for users whose ISPs support IPV6, or at least IPV6 tunneling over IPV4. Here is the situation in detail - mirrorselect tries a whole bunch of mirrors, including several IPV6-only mirrors - If your ISP *DOES NOT* support IPV6 (including IPV6 tunneling) things work OK. Attempting to contact the IPV6-only mirrors fails, and mirrorselect picks a bunch of IPV4-accessable mirrors, and things work OK. - If your ISP *DOES* support IPV6 (or at least IPV6 tunneling), you run into problems. Since hardly anyone is on IPV6, the IPV6-only mirrors have a lot less traffic, and are much more responsive to download requests. So mirrorselect's speed-tests will always favour the IPV6-only sites, and put them in your MIRRORS variable. Apparently, while the LiveCD has IPV6-enabled networking, the chrooted environment is IPV4-only. After chrooting, you have IPV4-only networking software trying to contact IPV6-only servers... oops. This is consistent with the problems reported on the mailing list, by *SOME* people (i.e. those whose ISP supports IPV6 in some manner). The solution to this problem is quite simple... - first chroot - then run mirrorselect This will cause mirrorselect to choose only servers that can be accessed from the chrooted environment. Today, this will result in mirrorselect only picking IPV4-accessable mirrors. Somewhere down the road, if/when the Gentoo install puts IPV6 networking into the chrooted environment, then mirrorselect will pick up IPV6 mirrors. """
Fixed in CVS.
