On Thu, Jul 13, 2000 at 07:01:28PM -0400, Olivier Galibert wrote:
> 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.
The underlying node is accessible to the translator, and this can and will
be used for example for filter (or for example for activity logging etc).
> 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".
Well, I think it is a useful feature and will be used (maybe optionally) in
translators. I have some ideas about it. It's the same in Linux, btw. You
can set mount point on existing directories with real content. Disallowing
this would inconvenience the users, too.
Thanks,
Marcus
--
`Rhubarb is no Egyptian god.' Debian http://www.debian.org Check Key server
Marcus Brinkmann GNU http://www.gnu.org for public PGP Key
[EMAIL PROTECTED], [EMAIL PROTECTED] PGP Key ID 36E7CD09
http://homepage.ruhr-uni-bochum.de/Marcus.Brinkmann/ [EMAIL PROTECTED]
