(Illustration by Gaich Muramatsu)
Michael, I think we fixed this - it is a bug. Pull down coda-4.7.?.tgz from carissimi.coda.cs.cmu.edu:/pub/peter I suggest that we first concentrate on file repair. Those utilities are in coda-src/egasr and are fairly easy to understand (I recommend you look at the source). I have done a little more on the pioctl code and played a little with PerlTk. It would be good to have a SpecPerl going. - Peter - Michael Stone writes: > I created a directory /coda/project/temp, then I tried to create a conflict by > doing a 'cfs wd' on two client machines. On each machine I created one common > and one unique file. I reconnected one machine, then the other. On the second > machine I now have this (as I should, right?): > > > ls -l /coda/project/temp > lr--r--r-- 1 root nogroup 27 Nov 10 20:24 /coda/project/temp -> > @7f000000.0000004d.0000388b > > When I run repair I get this: > > repair > begin /coda/project/temp > ENABLEREPAIR: /coda/project/temp/: Not a directory > > Now I'm confused. If I run 'cfs br' I get the global and local directories, > but I can't find any docs on what to do from there (everything points to the > repair tool). > > Mike StoneReceived on 1998-11-11 14:55:25