Re[2]: vn_fullpath() again

2005-09-06 Thread Igor Shmukler
Perhaps, I do not get it or maybe you are do not getting my point. There are times when resolving would not be possible or a name returned is not necessarily the one used when file was first accessed. We have discussed it here and everyone agreed on that. The hardlinks or files unlinked while vn

Re[2]: vn_fullpath() again

2005-09-06 Thread Robert Watson
On Tue, 6 Sep 2005, Igor Shmukler wrote: You are correct about the Unix file system organization, but does it mean reliable vnode to fullname conversation is not possible? Yes. Get over it. Well, I do not think it is a Yes. I very much think it is a No. You should have continued reading my

Re[2]: vn_fullpath() again

2005-09-06 Thread Igor Shmukler
> > You are correct about the Unix file system organization, but does it > > mean reliable vnode to fullname conversation is not possible? > > Yes. Get over it. Well, I do not think it is a Yes. I very much think it is a No. You should have continued reading my email 'til the middle or even far

Re[2]: vn_fullpath() again

2005-09-05 Thread Igor Shmukler
Robert, You are correct about the Unix file system organization, but does it mean reliable vnode to fullname conversation is not possible? As long as vnode is referenced we should be able to perform the lookup for any file system. Linux does a pretty good job with d_path() and I understand Matt