Karl, Thanks again. It is clear -- I think. But unless I'm still misunderstanding, you are giving me tools that I could use with my fingers on a keyboard and I'm wanting to build a program smart enough to look at static file pointers (fpointers) and resolve them to determine if they are pointing to the same place.
Susan -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Monday, March 12, 2007 4:19 PM To: [EMAIL PROTECTED] Cc: [email protected] Subject: RE: [U2] Help with File Pointers <quote who="Susan Joslyn"> > Hi Karl, > Thanks! The thing is, I can figure out where "I am", but I need to figure > out where two Fpointers are pointing. > > Say I have two Fpointers (VOC entries): > > 001 F > 002 ../../this.path/that.path/BANANA > 003 ../../this.path/that.path/D_BANANA > > And another > 001 F > 002 /u1/ud/this.path/that.path/BANANA > 003 /u1/ud/this.path/that.path/BANANA > > How do I determine for certain that they are (or are not) pointing to the > same exact file? If you SH out to a command prompt, then you can do cd <line 2 on each F-Ptr> minus the file itself. If you do this in 2 different command prompts, then type PWD in each, you'll see the exact path, and if it matches, then you are looking at the same file. This is one reason not to use relative file points to 'remote' files. It's better to use Q-pointers. I hope this is more clear that my previous feeble attempt. Karl > > Susan > > > -- Karl Pearson Director of I.T. ATS Industrial Supply, Inc. [EMAIL PROTECTED] http://www.atsindustrial.com 800-789-9300 x29 Local: 801-978-4429 Fax: 801-972-3888 "To mess up your Linux PC, you have to really work at it; to mess up a microsoft PC you just have to work on it." ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
