| 1 |
On Thu, Nov 18, 2010 at 11:21:33AM +0000, Neil Bothwick 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 |
> If you didn't know, HTH were the devs supposed to know? |
| 14 |
|
| 15 |
The devs *CHANGED AN EXISTING DEFAULT FLAG* from -ipv6 to ipv6. What |
| 16 |
percentage of the user base was running ipv6 a couple of years ago? Why |
| 17 |
couldn't they have left the default at -ipv6? Ever heard of "the |
| 18 |
principle of least surprise" aka "the principle of least astonishment"? |
| 19 |
See http://en.wikipedia.org/wiki/Principle_of_least_astonishment |
| 20 |
Unnecessarily changing defaults violates that principle in the worst way. |
| 21 |
|
| 22 |
There's an old saying... |
| 23 |
* good judgement is the result of experience |
| 24 |
* experience is the result of bad judgement |
| 25 |
|
| 26 |
As a result of my "experience" with the ipv6 flag, I no longer |
| 27 |
robo-update. Note that in the first post of this thread, I said... |
| 28 |
|
| 29 |
> I normally... |
| 30 |
> |
| 31 |
> emerge -pv --deep --update world | less |
| 32 |
> |
| 33 |
> ...before updating, to check for booby-traps. |
| 34 |
|
| 35 |
So you see, I did learn from my "experience". I do check for stuff |
| 36 |
like this now. As an additional safety measure, I also begin the USE |
| 37 |
variable with "-*". |
| 38 |
|
| 39 |
-- |
| 40 |
Walter Dnes <waltdnes@××××××××.org> |
Archives