[fonc] Unsolved problem solved in mac os x

[John Carlson]

This Mac OSX feature sounds exactly what I am looking for. Thanks!
---------- Forwarded message ----------
From: "JD Paley" <***@jdpaley.com>
Date: Oct 5, 2014 10:05 AM
Subject: A response (post rejected by autom. list mgr)
To: "John Carlson" <***@gmail.com>
Cc:

Subject: Re: [fonc] Unsolved problem in computer science? Fixing shortcuts.

Thought this was solved with two-way binding - bidirectional links so that
a pointer gets updated whenever the linked element moves. Or as in OS X
Finder's Aliases (vs Sym/Hard Links) keeping in the link file file both the
higher- and lower-level addresses (the resource name and its inode number).
When a followed Alias mismatches its target name, a search for the univocal
inode gets triggered.

JD Paley

[John Carlson]

Next: what if the file system operation is a copy paste cut - old
operation? Sounds like we may be back to copying garbage collectors.

Post by John Carlson
This Mac OSX feature sounds exactly what I am looking for. Thanks!
---------- Forwarded message ----------
Date: Oct 5, 2014 10:05 AM
Subject: A response (post rejected by autom. list mgr)
Subject: Re: [fonc] Unsolved problem in computer science? Fixing shortcuts.
Thought this was solved with two-way binding - bidirectional links so that
a pointer gets updated whenever the linked element moves. Or as in OS X
Finder's Aliases (vs Sym/Hard Links) keeping in the link file file both the
higher- and lower-level addresses (the resource name and its inode number).
When a followed Alias mismatches its target name, a search for the univocal
inode gets triggered.
JD Paley