Sure makes sense to me. When I copy a file from ext2 to reiserfs 3 for instance we should make sure the save all the extra EA's and stuff like that in a special .#file.ext2.ea file. Then when I copy that to a XFS partition over NFS I should have a special .%filename.xfs.stf file, oh and then since I am using nautilas for that last transaction it should save it's own .Nautinfo file then when I copy that file to a Mac share then back to a ext3 filing system I should add the normal ._filename stuff, so I end up with a grand total of:
filename
._filename
.#filename.ext2.ea
.%filename.xfs.stf
.Nautinfo
.DS_Store
._.Nautinfo
._#filename.ext.ea
._%filename.xfs.stf
.%#filename.ext2.ea.xfs.stf
Seems like it makes sense to me. After all we don't want to give up any features or anything..
My only question is what happens after you copy the file to a Fat16 partition? 😛
filename
._filename
.#filename.ext2.ea
.%filename.xfs.stf
.Nautinfo
.DS_Store
._.Nautinfo
._#filename.ext.ea
._%filename.xfs.stf
.%#filename.ext2.ea.xfs.stf
Seems like it makes sense to me. After all we don't want to give up any features or anything..
My only question is what happens after you copy the file to a Fat16 partition? 😛