Re: [gentoo-user] One machine sends "emerge" text output to stderr, not stdout

["Walter Dnes" <waltdnes@waltdnes.org>]

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 <G>.

-- 
Walter Dnes <waltdnes@waltdnes.org>