| 1 |
On Fri, 19 Nov 2010 01:34:15 -0500, Walter Dnes wrote: |
| 2 |
|
| 3 |
> > Blaming the devs for your broken modem/router is rather unfair. If |
| 4 |
> > you'd known it was unable to handle IPv6 correctly, why didn't you |
| 5 |
> > set the flag accordingly? |
| 6 |
> |
| 7 |
> My ISP didn't support ipv6 at that time. They're now running a beta |
| 8 |
> for native ipv6 (no tunneling) but I don't have the time to play with |
| 9 |
> bleeding edge stuff. Regardless of the fact that my router/modem does |
| 10 |
> or does not support ipv6, if I don't have ipv6 service from my ISP (or a |
| 11 |
> tunnel broker) ipv6 is pointless. |
| 12 |
|
| 13 |
But harmless. The severe delays you noticed were the result of a broken |
| 14 |
modem/router failing to recognise that IPv6 was not available and trying |
| 15 |
to use it anyway. The usual fix for such a problem is a firmware update. |
| 16 |
|
| 17 |
I don't use -*, I did see the ipv6 flag pop up in emerge -uaD world, I |
| 18 |
disabled it. I supposed it comes down to how much you trust yourself and |
| 19 |
the devs. |
| 20 |
|
| 21 |
Incidentally, you are better off not using -v in this situation because |
| 22 |
then only changed flags are shown. I still have to get out of the habit |
| 23 |
of using it, gained years ago when portage didn't shown any use details |
| 24 |
when you didn't use -v. |
| 25 |
|
| 26 |
|
| 27 |
-- |
| 28 |
Neil Bothwick |
| 29 |
|
| 30 |
Definition of Trust: Two cannibals having oral sex. |
Archives