[Coco] [Color Computer] What happend to http://www.nitros9.org/

[Gene Heskett]

On Tuesday 20 February 2007, Boisy Pitre wrote:
>Brian,
>
>Have you tried using CVS to pull down the NitrOS-9 repository to your
>system?  If so, please report the results, along with exact commands
>used and errors received.
>
>CVS has been used successfully to bring the project along for almost
>10 years now.  Any problems that I've seen people having with CVS
>came about through their own ignorance and not with any fault of the
>system itself.  It is solid software.
>
>If you want to download NitrOS-9 disk images, then you don't need
>CVS; however, if you plan on doing development, then CVS is a must to
>both obtain and contribute source code to the project.
>
>Again, I am asking for those who have actually tried to use CVS to
>pull down the NitrOS-9 repository from SourceForge to respond with
>their results.
>
>Boisy
>
>On Feb 20, 2007, at 3:50 PM, Brian Blake wrote:
>> Due to issues similar to Gene's experience, I do not mess with cvs.
>> At all. If I need something that can only be gotten via cvs, I find
>> something else to use in it's place. Granted, that's a bad plan of
>> action for NitrOS9...
>>
>>
>> Brian
Here is a clue, it may be that verizon is screwing with sites they 
seem to think are the bandwidth wasters with no kickbacks coming in:
Outputs from a traceroute:

[root at coyote channels]# traceroute google.com
traceroute to google.com (64.233.167.99), 30 hops max, 40 byte packets
 1  router.coyote.den (192.168.71.1)  0.303 ms  0.427 ms  0.530 ms
 2  10.8.1.1 (10.8.1.1)  30.102 ms  33.119 ms  35.137 ms
 3  at-0-3-0-1711.CORE-RTR2.CLRK.verizon-gni.net (130.81.12.65)  39.083 ms  41.115 ms  43.959 ms
 4  so-3-1-1-0.BB-RTR1.PHIL.verizon-gni.net (130.81.20.150)  59.425 ms  61.762 ms  64.487 ms
 5  130.81.17.153 (130.81.17.153)  65.963 ms  69.027 ms  71.943 ms
 6  POS2-0.GW1.PHL16.ALTER.NET (152.63.38.133)  148.886 ms  150.542 ms  153.397 ms
 7  0.so-3-0-0.CL2.PHL6.ALTER.NET (152.63.43.38)  91.232 ms  46.552 ms  49.285 ms
 8  0.so-6-2-0.XL2.IAD8.ALTER.NET (152.63.32.34)  51.107 ms  54.309 ms  57.286 ms
 9  0.so-7-0-0.BR1.IAD8.ALTER.NET (152.63.32.161)  60.130 ms  63.062 ms  65.833 ms
10  4.68.127.21 (4.68.127.21)  75.236 ms  77.920 ms  80.924 ms
11  so-2-1-0.bbr2.Washington1.Level3.net (209.244.11.13)  84.872 ms  88.112 ms  55.270 ms
12  ae-0-0.bbr1.Chicago1.Level3.net (64.159.1.33)  75.547 ms  77.266 ms  80.251 ms
13  ae-11-51.car1.Chicago1.Level3.net (4.68.101.2)  72.773 ms  75.418 ms ae-21-54.car1.Chicago1.Level3.net (4.68.101.98)  76.556 ms
14  GOOGLE-INC.car1.Chicago1.Level3.net (4.79.208.18)  81.477 ms  85.136 ms  87.177 ms
15  66.249.94.133 (66.249.94.133)  91.165 ms  93.449 ms  96.184 ms
16  64.233.175.26 (64.233.175.26)  102.264 ms 72.14.232.70 (72.14.232.70)  104.487 ms  105.208 ms
17  py-in-f99.google.com (64.233.167.99)  69.168 ms  73.417 ms  75.043 ms

That was as fast as traceroute could write to my screen.

[root at coyote channels]# traceroute sourceforge.net
traceroute to sourceforge.net (66.35.250.203), 30 hops max, 40 byte packets
 1  router.coyote.den (192.168.71.1)  0.325 ms  0.445 ms  0.532 ms
 2  10.8.1.1 (10.8.1.1)  30.249 ms  32.977 ms  35.980 ms
 3  * * *
 4  so-2-1-1-0.BB-RTR1.RES.verizon-gni.net (130.81.20.148)  67.054 ms  69.519 ms  73.232 ms
 5  so-6-0-0-0.ASH-PEER-RTR2.verizon-gni.net (130.81.17.177)  74.722 ms  77.749 ms  79.791 ms
 6  0.so-7-0-0.XL2.IAD8.ALTER.NET (152.63.36.205)  82.794 ms  85.645 ms  88.301 ms
 7  0.so-4-2-0.XT2.DCA5.ALTER.NET (152.63.40.42)  101.564 ms  72.472 ms  70.411 ms
 8  0.so-7-0-0.BR1.DCA5.ALTER.NET (152.63.43.177)  64.951 ms  47.515 ms  47.297 ms
 9  cpr1-pos-6-2.VirginiaEquinix.savvis.net (208.173.10.137)  48.793 ms  50.093 ms  49.881 ms
10  bcs2-so-5-0-0.Washington.savvis.net (206.24.238.217)  50.982 ms  49.830 ms  49.829 ms
11  bcs1-so-7-0-0.Washington.savvis.net (204.70.192.33)  52.066 ms  50.989 ms  84.629 ms
12  dcr1-so-0-3-0.Chicago.savvis.net (204.70.192.26)  73.043 ms  82.010 ms  75.312 ms
13  dcr2-so-5-0-0.Chicago.savvis.net (204.70.192.46)  74.992 ms  74.642 ms  69.278 ms
14  dcr1-so-4-3-0.Denver.savvis.net (204.70.193.225)  98.918 ms  98.887 ms  99.330 ms
15  dcr2-so-1-1-0.SanFranciscosfo.savvis.net (204.70.193.218)  129.807 ms  129.864 ms  129.085 ms
16  bhr1-pos-0-0.SantaClarasc8.savvis.net (208.172.156.198)  130.075 ms  130.340 ms  131.952 ms
17  csr1-ve243.santaclarasc8.savvis.net (66.35.194.50)  129.509 ms  129.904 ms  130.827 ms
18  66.35.212.174 (66.35.212.174)  137.127 ms  133.253 ms  134.969 ms
19  sourceforge.net (66.35.250.203)  130.226 ms !X  129.509 ms !X  127.654 ms !X

This took several seconds, paused at the clarksburg hub.

I believe a call to tech support is in order.  Better yet, I threatened 
to contact the fcc and object to their status as a common carrier 2 days
ago when it became obvious they were filtering any and all email from
ekiga.org, whom they view as a competitor in the VOIP business.  They
would filter skype too if they could ever figure out how skype is getting
past their monitors now.

There is one other game in town, I could get cable and then sign up for
their service, at a combined price well in excess of $130 a month.

We seriously need an FCC with teeth and that is not in bed with half the
stuff they should be regulating.  But congress doesn't like that, so
they're running the commission on 25% (relatively speaking) of the
funding level they had back in the 50's.

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Yahoo.com and AOL/TW attorneys please note, additions to the above
message by Gene Heskett are:
Copyright 2007 by Maurice Eugene Heskett, all rights reserved.