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 1PJg3u-0002lK-Nb for garchives@archives.gentoo.org; Sat, 20 Nov 2010 05:32:34 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 0FB00E0789; Sat, 20 Nov 2010 05:31:07 +0000 (UTC) Received: from ironport2-out.pppoe.ca (ironport2-out.teksavvy.com [206.248.154.181]) by pigeon.gentoo.org (Postfix) with ESMTP id 01441E0789 for ; Sat, 20 Nov 2010 05:31:06 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AugKAGvr5kxMCodc/2dsb2JhbACUYI0GfHK7eoVLBIRaiRqETA X-IronPort-AV: E=Sophos;i="4.59,227,1288584000"; d="scan'208";a="83040788" Received: from 76-10-135-92.dsl.teksavvy.com (HELO waltdnes.org) ([76.10.135.92]) by ironport2-out.pppoe.ca with SMTP; 20 Nov 2010 00:31:05 -0500 Received: by waltdnes.org (sSMTP sendmail emulation); Sat, 20 Nov 2010 00:32:28 -0500 From: "Walter Dnes" Date: Sat, 20 Nov 2010 00:32:28 -0500 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] One machine sends "emerge" text output to stderr, not stdout Message-ID: <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> 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: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20101119092518.1257aa8b@digimed.co.uk> User-Agent: Mutt/1.5.20 (2009-06-14) X-Archives-Salt: e50dc476-2aec-469d-8153-f69ba17386e9 X-Archives-Hash: 1fa178a581d2c90c28cc634b021b37f3 On Fri, Nov 19, 2010 at 09:25:18AM +0000, Neil Bothwick 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. It's more complex than that. How is the IPV6-enabled browser or media player supposed to know that my modem doesn't support IPV6 and neither does my ISP and neither do umpteen hops between me and the site I'm trying to connect to? See http://www.ipjforum.org/?p=378 > The technology in web browsers and operating systems involves doing > Domain Name System (DNS) queries for AAAA and A resource records and > then attempting to connect to the resulting IPv6 and IPv4 addresses > sequentially. If the IPv6 path is broken (or slow), this connection > can take a long time before it falls back to trying IPv4. This process > is especially painful on typical websites that retrieve objects > from different hosts-each failure incurs a delay. The combination of > operating system and web browser results in delays from 20 seconds to > several minutes if the IPv6 path is broken[2]. The typical message > flow of a TCP client is shown in Figure 1. Clearly, this delay is > unacceptable to users. Users avoid this delay by disabling IPv6[3] > or avoiding IPv6-enabled websites. The decision to enable IPV6 by default was a mistake. The only beneficial side effect was that it taught me not to do robo-updates any more . -- Walter Dnes