i think the source of the problem usually is that references are not
encoding the intention properly (certainly in the case of symlinks).
let's consider references in the context of e.g. a computer programs:
in prevalent programming languages/systems a call site is referencing
a function by a
Interesting..
Last time a thought about this I figured that a solution could be to split
identity from location.
That is, the location of a file is currently part of its identity, so when
you moved it, all links that refer to it break. If, however, all files
where given a unique identifier (a
On Tue, Oct 7, 2014 at 11:29 AM, Fernando Cacciola
fernando.cacci...@gmail.com wrote:
I do realise of course that maintaining a gigantic master index of all
files is not applicable to the real world, but nonetheless I think the
general form of the solution (split identity from location) is
The problem with fixing shortcuts in file-systems, and with links and with
names and with files in filesystems in general, is that the intention of the
link, and even of a filename is not clear.
For a simple example, compare a jpeg of your cat to a configuration file, e.g.
/etc/passwd.
It is
Context below, sorry about the top-post (stupid smartphone.)
I think I remember that in Xanadu, links are two-way streets. When you move
the link, I can only assume that both of those pointing devices would need to
be updated.
I'm not sure how it works though. Is there a central authority
There are two assumptions that do not generally hold.
1) Both sides of links are always available at the same time (not true in
case of NFS that is often symlinked). Just consider the case of notebook
taken home and file system change in mean time.
2) There is a permission to change file system on
