Pavel Machek <pavel@xxxxxx> said:.elastic is a file or directory? If its file, daemon has to do the ugly insertion deletion of the file enteries. If its a directory, daemon has to do the updating of the files in case of mv, plus follow the links for unlink, chown if we are storing the files as symlinks and we will be wasting the inodes.
Case closed, anyway. It belongs in the kernel only if there is no
reasonable way to do it in userspace.
But... there's no reasonable way to do this in userspace.
Two pieces of kernel support are needed:
1) some way to indicate "this file is elastic" (okay perhaps xattrs
can do this already)
Or just a list of elastic files in ~/.elastic. Even better, could mark them
as "Just delete", "compress"; could go as far as giving (fallback?) globs
to select files for each treatment ("If space gets tight, delete *~ files,
and compress *.tex that haven't been read in a week"). Sounds like a fun