Currently the on-disk structures for translators in ext2 allow for an
inode to be both a passive translator and a file (or directory) with
actual contents. AFAICT, this capability is not used anywhere for
now. I'm not even sure it is accessible from the filesystem
interface.
My question is, do we really need this capability, or would a on-disk
implementation of translators which would use the same allocation
scheme as files (or symlinks, probably) would be ok? That would
remove the block pointer in osd1 and only use one bit in the inode
flags to say "this is a translator".
Thoughts?
OG.
