Why should links be in the filesystem, rather than an application / UI construct? Why should there be 1 filesystem, rather than 0, or thousands? Why must a filesystem be a DAG + links, rather than some other graph, or a soup with a lot of queries? Why should a "link" simply be a file pretending to be in two directories at once, rather than a data-carrying relationship between two nodes in the graph?
I think these are much more interesting questions :) -- "Enjoy every sandwich." - WZ Josh 'G-Funk' McDonald - j...@joshmcdonald.info On 10 October 2014 09:49, Daniel W Gelder <daniel.w.gel...@gmail.com> wrote: > The original question seems to be how to maintain links when the file is > moved or renamed. Perhaps the file could have a unique ID in the file > system, and the link would try the given pathname, but if it's not there, > try the unique ID. Would that work? > > _______________________________________________ > fonc mailing list > fonc@vpri.org > http://vpri.org/mailman/listinfo/fonc > >
_______________________________________________ fonc mailing list fonc@vpri.org http://vpri.org/mailman/listinfo/fonc
