It started when I went to do my first pull
    of the OpenEmbedded database

$ mtn --db=OE.mtn pull monotone.nslu2-linux.org org.openembedded.dev
mtn: doing anonymous pull; use -kKEYNAME if you need authentication
mtn: connecting to monotone.nslu2-linux.org
mtn: first time connecting to server monotone.nslu2-linux.org
mtn: I'll assume it's really them, but you might want to double-check
mtn: their key's fingerprint: 0d63ffa0fad7729bafd3428d29b28da7b61fac4d
mtn: finding items to synchronize:
mtn: certificates | keys | revisions
and the count slowly rising into the tens of thousands....

    Things chugged along for a few hours, until my power flicked off.
    After the power glitch, (and my installing a surge suppressor!)
    I restarted monotone.

address@hidden:/home/eliyahu/stuff$ mtn --db=OE.mtn pull monotone.nslu2-linux.org org.openembedded.dev
mtn: doing anonymous pull; use -kKEYNAME if you need authentication
mtn: connecting to monotone.nslu2-linux.org
mtn: finding items to synchronize:
mtn: certificates | keys | revisions
mtn:       76,633 |   76 |    25,247
mtn:  bytes in | bytes out | certs in | revs in
mtn:     1.1 M |   993.1 k |        0 |       0
mtn:  bytes in | bytes out |    certs in | revs in
mtn:     7.9 M |   993.1 k | 2,214/2,215 | 546/546
mtn:  bytes in | bytes out |    certs in
mtn:     7.9 M |   993.1 k | 2,215/2,215          
mtn: error: I/O failure while talking to peer monotone.nslu2-linux.org, disconnecting

    So after this second hang, for reasons unknown to me,
    I started it up a third time.

address@hidden:/home/eliyahu/stuff$ mtn --db=OE.mtn pull monotone.nslu2-linux.org org.openembedded.dev
mtn: doing anonymous pull; use -kKEYNAME if you need authentication
mtn: connecting to monotone.nslu2-linux.org
mtn: finding items to synchronize:
mtn: certificates | keys | revisions
mtn:       78,295 |   76 |    25,793
mtn:  bytes in | bytes out | certs in
mtn:         0 |       177 |        0
mtn: fatal: std::runtime_error: network error: recv failure: Connection timed out
mtn: this is almost certainly a bug in monotone.
mtn: please send this error message, the output of 'mtn version --full',
mtn: and a description of what you were doing to address@hidden
mtn: failed to write debugging log to /home/dakyaro/.monotone/dump

    I thought I would try to find out what was up with that last line,
    so I checked and discovered what is certainly a SEPARATE bug

address@hidden:/home/eliyahu/stuff$ ls -ld /home/dakyaro/.monotone
ls: cannot access /home/dakyaro/.monotone: No such file or directory

    monotone SHOULD verify that ~/.monotone exists when it starts up,
    and either complain or silently create the directory, instead of
    hanging at the end.
    So I fixed that problem... and got the rest of the information for you.

address@hidden:/home/eliyahu/stuff$ mkdir !$
mkdir /home/dakyaro/.monotone
address@hidden:/home/eliyahu/stuff$ mtn version --full
monotone 0.40 (base revision: 5ccc279f9dea0444b47f03dd5291ecc985fcb7f6)
Running on          : Linux 2.6.26-1-686 #1 SMP Wed Aug 20 12:56:41 UTC 2008 i686
C++ compiler        : GNU C++ version 4.3.1
C++ standard library: GNU libstdc++ version 20080725
Boost version       : 1_34_1
Changes since base revision:
unknown