Re: Directory???

On Thu, 2005-07-21 at 20:41 +1000, Keith Bainbridge wrote:
> G'day folks,
> 
> What do youthink I have done to get this:
> 
> /disks/net/b120/hda4/home/keith/.cxoffice/dotwine/dosdevices/ZSXKM0
> ~L/proc/14543/task/14543/root/proc/14543/task/14543/root/proc/14543
> /task/14543/root/proc/14543/task/14543/root/proc/14543/task/14543/r
> oot/proc/14543/task/14543/root/proc/14543/task/14543/root/proc/1454
> 3/task/14543/root/proc/14543/task/14543/root/proc/14543/task/14543/
> root/proc/14543/task/14543/root/proc/14543/task/14543/root/proc/145
> 43/task/14543/root/proc/14543/task/14543/root/proc/14543/task/14543
> /root/proc/14543/task/14543/root/proc/14543/task/14543/root/proc/14
> 543/task/14543/root/proc/14543/task/14543/root/proc/14543/task/1454
> 3/root/proc/14543/task/14543/root/home/keith/keithdata/steph/etax20
> 03/LUKE.TAX
> 

Ran "find" over the /proc directory and passed the result to something
else that creates files?

/proc/<PID>/task/<PID>/root is (usually) a symlink to "/", so that kind
of makes all the middle part of that path make sense. Why this path got
constructed out of parts of your personal files and a recursion
over /proc will be interesting to hear :)

Perhaps CrossOver Office is looking in /proc and treating it like a
normal filesystem?

Or maybe the shell got passed some odd combination of characters that
"resolved" to the PID entry in /proc ?

Cheers, Ben