> Hurd is definitely using the translator field, and I only
> recently discovered they are using it to point at a disk block
> where the name of the translator program (I'm not 100% sure, but
> I think it's a generic, out-of-band, #! sort of functionality).
Translators on directories are a combo of automount+userland
filesystem, with the addition on having them saved in the
mounted-on filesystem. Rather nice actually. Replacing /etc/fstab
with local-to-the-mountpoint information has some charm. I'm not
sure if translator-on-files actually exist.
You can set a translator on a file or a directory, it doesn't matter.
Anything that is accessed through the file-system is a translator.
/dev/null is a translator, symbolic links can be[0] translators,
/dev/hd0s1 (/dev/hda1 in GNU/Linux) is a translator, ...
[0]: They are usually implemented directly into the file-system so you
don't end up spawning a new processes for each symlink. But if the
file-system in question doesn't support symlinks you can always use
the symlink translator to get symlinks. This will work for all
file-systems as long as you do not wish to have it persitant across
reboots, then you need passive translator support (which is what those
fields in ext2 are for among other things).
Happy hacking.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
