3 ms·
I spent sometime yesterday thinking about what queries I would like a filesystem (layout) to be able to answer. -installed programs -files installed (except c
by im3w1l 13y ago
I spent sometime yesterday thinking about what queries I would like a filesystem (layout) to be able to answer.
-installed programs
-files installed (except configuration) by a program
-files installed (including configuration) by a program
-libraries
-a users personal files (including configuration).
-all files except bare bones install
-all files
-files on a specific hard drive
My conclusion was that my preferred layout would be
/os/ - bare bones install
/home/ - users files
/home/im3w1l/.conf/firefox - my configuration for firefox
/programs/ - installed program and libraries
/programs/libfuse/.conf - configuration for libfuse
/programs/firefox/.conf/im3w1l - my configuration for firefox
C:/programs - installed programs on specific hard drive
And that if a file is deleted from one place it is deleted from all. So
rm /home/im3w1l/.conf/firefox -rf
would be the same as
rm /programs/firefox/.conf/im3w1l -rf
But I think a general tagged system has some problems, most notable filename collisions. Adding a tag to a file could create a collision for instance.
- loup-vaillant 13y agoFor me a basic tag based file system needs several things: A unique ID for files (a strong cryptographic hash of the contents is probably best), a name for each file, and a list of tags for each files. And of course, a number of logical volumes on which the files are "located". Where a directory structure is actually needed, files could have special names, like "/os/glad/file_42" (that's a name, not a path). A variation on this theme would be to do away with explicit names altogether, and only use tags. The "name" of the file would just need to be reasonably unique. That one is probably best. Now, when you search for a file, you just query for tags. Can also be done through the shell: it's just that those two commands would have the exact same effect: cd /foo/bar cd /bar/foo As for the volume, you need them to transfer files between your USB key and your computer. Oh, thinking of using cryptographic hashes to name files… When you modify the file, the ID changes as well… that's a new file! By default, the old version should still be around. Imagine that: Git for the masses.