Re: Get login name and/or path to home directory of current user?

In article <DJqdnWbSz8WR8P7bnZ2dnUVZ_ragnZ2d@[EMAIL PROTECTED]
>,
 russotto@[EMAIL PROTECTED]
 (Matthew T. Russotto) wrote:

> In article
<gandreas-1F344A.11003801062007@[EMAIL PROTECTED]
>,
> glenn andreas  <gandreas@[EMAIL PROTECTED]
> wrote:
> 
> >And even more semantically, a path need not identify anything at all, 
> >nor does it uniquely identify it either (since more than one path may 
> >point to the same file system object).
> >
> >In Unix, what identifies a file system object on disk is an inode.
> 
> HFS+ lacks inodes.

The point was how Unix identifies file systems objects, and that is via 
inodes.  In order for OS X to sup****t the Unix model, it needs inodes on 
all file systems, and this includes HFS+.

As a result, when needed, a "virtual" inode number will be created to 
provide sup****t for that programming model (this is all magically done 
in the kernel, though it does have some semantic problems with how 
ExchangeData() works).  

And actually, the converse will also happen - in MacOS you can open a 
file by the "file ID", so the Unix file tree will include things like 
the ".vols" directory to sup****t this.


See <http://www.wsanchez.net/papers/USENIX_2000/>
for a whole lot more 
details on how Unix and Mac OS environments were integrated.