More in the saga of the coda client: My machine was definitely
unhappy.  It would not run shutdown after the failed coda-client
startups.  After resetting (using the reset button, not shutdown), I
had to run fsck manually and fix up a bunch of problems.  Sure would
be nice if coda-client didn't trash my other partitions....

Anyway, I also do not see testserver.  It looks like something goes
wrong after gw.cs.cmu.edu.

% /usr/sbin/traceroute testserver.coda.cs.cmu.edu
traceroute to JEPTHE.ODYSSEY.CS.CMU.EDU (128.2.185.182), 30 hops max, 40 byte packets
 [...]
 3  bifrost.net.yale.edu (130.132.1.100)  2.578 ms  1.79 ms  1.823 ms
 4  border7-serial4-6.WestOrange.mci.net (204.70.71.113)  29.94 ms  36.889 ms  30.531 ms
 5  core2-fddi-0.WestOrange.mci.net (204.70.64.49)  34.765 ms  29.653 ms  29.349 ms
 6  core1.WillowSprings.mci.net (204.70.4.173)  209.064 ms  775.419 ms  65.004 ms
 7  border4-fddi-0.WillowSprings.mci.net (204.70.104.35)  124.682 ms  64.009 ms  106.564 ms
 8  psc-hssi.WillowSprings.mci.net (204.70.108.6)  77.698 ms  58.649 ms  76.395 ms
 9  backbone-cmu.psc.edu (192.88.114.36)  70.325 ms  62.693 ms  58.031 ms
10  GW.CS.CMU.EDU (128.2.1.8)  79.756 ms  59.874 ms  65.829 ms
11  * * *
12  * * *
13  * * *
14  * * *
15  * *

and it seems to be stuck forever....


Also, if it would help, I could make the binary rpm available that
works under the 2.0.30 kernel.  But since I haven't been able to test
it I am reluctant to release the binaries.  They do seem to behave in
the "standard" way, however.

-Bradley