From: Maxim L. <zel...@ma...> - 2008-05-24 11:17:59
|
hi all I'm interested in a filesystem with the certain features. It might exist already, but I'm not aware of it, if it is not I'll probably try to implement it myself (I'm not a good system programmer though...) The idea of this filesystem is that it should "remember" move and rename operations on files and if some program try to access the old destination of moved file, the filesystem should redirect it to new destination. This is simple case, more complicated functionality can include automatic fix for symlinks if source file is moved/renamed - this functionality known as "Alias" http://en.wikipedia.org/wiki/Alias_(Mac_OS) There are a lot of reasons for having such filesystem, for example: I usually need to postprocess some experimental data, at very first moment there is only one file /home/user/experiments/data.dat and I plot it with gnuplot. So the path is hardwired in data.gnu script or even worse: in many scripts scattered in different directories and ore projects. After a while I get more data from the same experiment and moved all the files to /home/user/experiments/series0/data?.dat, data0.dat being the first one. Noone can plan directory structure apriory, and creation symlinks every time a file is moved/renamed result in big mess on hard drive very soon. Finally all my *.gnu scripts do not work anymore! I have to edit all them manually (and find all of them before), it is good if all of them are text files, but path might be hardwired to an openoffice binary file or already archived in tar.gz file. Mac OS Aliases could probably help in this particular case (I'm not sure though), but there are plenty of more general cases... I know that such a filesystem is somewhat related to "Semantic File System" like WinFS or Tagsistant implemented in fuse, also it is quite close to Tenor developed for KDE4 (IMHO it should be on fylesystem level). I cannot find a real working implementation of described features. Could anybody suggest something? If not, it might be implemented in fuse, the history of file modification can be stored for example in file/directory metadata and can be used for redirection. File deletion/copying should be handled appropriately... Actually suggestions are welcome! best Maxim |
From: Antonio M. <ame...@ic...> - 2008-05-24 12:15:31
|
On Sat, 24 May 2008 18:17:50 +0700 Maxim Loginov <zel...@ma...> wrote: > hi all > > I'm interested in a filesystem with the certain features. It might > exist already, but I'm not aware of it, if it is not I'll probably > try to implement it myself (I'm not a good system programmer > though...) The idea of this filesystem is that it should > "remember" move and rename operations on files and if some program > try to access the old destination of moved file, the filesystem > should redirect it to new destination. This is simple case, more Maybe I'm missing something, but why don't you use *hard* links? Hard links are, basically, another entry in a directory pointing to the original file. If you move or rename the "original"[1] file the hard link will still points to it. .a. [1] Actually, you cannot tell which filename was the "original"... -- Antonio Messina System and Network Administrator, Software Engineer email: ant...@ic... | The Abdus Salam ICTP phone: +39 040-2240-691 | Strada Costiera, 11 fax: +39 040-2240-7691 | 34016 Trieste, Italy |