From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1PJp0w-0002Bp-Cp for garchives@archives.gentoo.org; Sat, 20 Nov 2010 15:06:06 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id EE428E07F7; Sat, 20 Nov 2010 15:05:03 +0000 (UTC) Received: from mail.digimed.co.uk (82-69-83-178.dsl.in-addr.zen.co.uk [82.69.83.178]) by pigeon.gentoo.org (Postfix) with ESMTP id B2833E07BA for ; Sat, 20 Nov 2010 15:05:03 +0000 (UTC) Received: from digimed.co.uk (grunthos.digimed.co.uk [192.168.1.4]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mail.digimed.co.uk (Postfix) with ESMTPSA id 1C6C5499E53 for ; Sat, 20 Nov 2010 15:05:00 +0000 (GMT) Date: Sat, 20 Nov 2010 15:04:54 +0000 From: Neil Bothwick To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] One machine sends "emerge" text output to stderr, not stdout Message-ID: <20101120150454.59c421ab@digimed.co.uk> In-Reply-To: <20101120053228.GA1990@waltdnes.org> References: <20101117002517.GA18328@waltdnes.org> <20101118002025.GA23732@waltdnes.org> <20101118112133.45a5c999@digimed.co.uk> <20101119063415.GE32524@waltdnes.org> <20101119092518.1257aa8b@digimed.co.uk> <20101120053228.GA1990@waltdnes.org> Organization: Digital Media Production X-Mailer: Claws Mail 3.7.7 (GTK+ 2.20.1; i686-pc-linux-gnu) X-GPG-Fingerprint: 7260 0F33 97EC 2F1E 7667 FE37 BA6E 1A97 4375 1903 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=PGP-SHA1; boundary="Sig_/es=3wKUSYz0V2svXm4SWtbk"; protocol="application/pgp-signature" X-Archives-Salt: 614da5e9-1312-4dc4-920d-5e90bdf67a75 X-Archives-Hash: 0d851e948ee308f378a67da352e43b7e --Sig_/es=3wKUSYz0V2svXm4SWtbk Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Sat, 20 Nov 2010 00:32:28 -0500, Walter Dnes wrote: > > But harmless. The severe delays you noticed were the result of a > > broken modem/router failing to recognise that IPv6 was not available > > and trying to use it anyway. The usual fix for such a problem is a > > firmware update. =20 >=20 > It's more complex than that. How is the IPV6-enabled browser or media It's not the browser, its the resolver, the delays are caused by excessively long DNS lookups. > player supposed to know that my modem doesn't support IPV6 The modem tells it and the resolver falls back to IPv4. The problem occurs when the modem doesn't know that it doesn't support IPv6 (or even what IPv6 is, which is why a firmware update usually fixes it) so the resolver doesn't try IPv4 until the IPv6 request times out. Using 21st Century software with 20th Century hardware is asking for such problems :( --=20 Neil Bothwick I am McCoy of Bo...Damnit! I'm a doctor, not a collective! --Sig_/es=3wKUSYz0V2svXm4SWtbk Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) iEYEARECAAYFAkzn45oACgkQum4al0N1GQOP6QCfd+GUW5RRWCBgBnaonF/QkILu yGsAoK0vLo5EWeFsJG0vzlVhHZB849e5 =v28K -----END PGP SIGNATURE----- --Sig_/es=3wKUSYz0V2svXm4SWtbk--