Re: Creating unique numerical representation of file path?
Re: Creating unique numerical representation of file path?
- Subject: Re: Creating unique numerical representation of file path?
- From: Andrei Tchijov <email@hidden>
- Date: Sat, 13 Oct 2007 20:43:00 -0400
good point. though it may be viewed as an extra benefit -- if you do
not want to import multiple links to the same file.
On Oct 13, 2007, at 8:35 PM, Mark J. Reed wrote:
Also,it's worth noting that inodes represent the file, not the path to
the file. In UNIX filesystems a given file may appear under multiple
pathnames. Aside from the standard "." and ".." entries in
directories, hard links aren't much used, so it's not likely to be a
problem in practice, but worth knowing.
Example:
$ echo Hello >hello1.txt
$ ln hello1.txt hello2.txt
$ cat hello2.txt
Hello
$ ls -1i hello?.txt
7128053 hello1.txt
7128053 hello2.txt
$ echo goodbye >hello2.txt
$ cat hello1.txt
goodbye
On 10/13/07, Mark J. Reed <email@hidden> wrote:
Inode numbers are per-filesystem. The root folder of each volume
will
be inode number 2, for instance.
--
Mark J. Reed <email@hidden>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
AppleScript-Users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
Archives: http://lists.apple.com/archives/applescript-users
This email sent to email@hidden