> When I run 'pull' it just produces no output and just sits there
> apparently for ever. I can run '9fs sources' and navigate around in
> /n/sources/. Is there a lock file or something I should delete? Any
> suggestions for debugging?
> 
I was going to raise the alarm before, but too many other priorities
put Plan 9 on backburner.

That said, I abandoned a "pull -v" to its own devices and I see that
it actually overcame obstacles and proceeded past the blocking point.
I left it running when it reached:

        ...
        d sys/man/4/sacfs 664 sys sys 1338508171
        d 386/ld.com 775 sys sys 1252805896
        d 386/bin/disk/sacfs 775 sys sys 1020319075
        d 386/bin/disk/mksacfs 775 sys sys 1020319074
        d 386/9pxeloaddebug 775 sys sys 1316634597
        d 386/9pxeload 775 sys sys 1316634597
        d 386/9loadlitedebug 775 sys sys 1316634596
        d 386/9loadlite 775 sys sys 1316634596
        d 386/9loadask 775 sys sys 1316634596
        c sys/src/cmd/venti/srv/bloom.c
        c sys/man/8/6in4
        c sys/src/libc/9sys/nsec.c
        c sys/src/cmd/6c/cgen.c
        c sys/src/9/omap/fpiarm.c
        c sys/src/9/bitsy/fpiarm.c

and sat, and sat, and sat.

But I see now that it got going again, no idea when or how long after
the above:

        c sys/src/9/bitsy/mmu.c
        c sys/src/9/kw/fpiarm.c
        ! sys/lib/man/lookman/index: locally modified; will not overwrite
        ! sys/man/1/INDEX: locally modified; will not overwrite
        ! sys/man/1/INDEX.html: locally modified; will not overwrite
        ! sys/man/8/INDEX: locally modified; will not overwrite
        ! sys/man/8/INDEX.html: locally modified; will not overwrite
        c sys/src/cmd/unix/drawterm/Make.unix
        a sys/src/cmd/unix/drawterm/posix-arm 20000000775 sys sys 1341726550
        a sys/src/cmd/unix/drawterm/posix-arm/Makefile 664 sys sys 1341726493
        a sys/src/cmd/unix/drawterm/posix-arm/getcallerpc.c 664 sys sys 
1341726493
        a sys/src/cmd/unix/drawterm/posix-arm/md5block.c 664 sys sys 1341726493
        ...

so maybe patience is the critical issue here?  Or an error somewhere?

I'm going to try again.  Yep, it seems to jam somewhere, if it unjams
I'll let the list know.

++L


Reply via email to