Mo McKinlay wrote:
>
> # - Tar-copyable.
>
> # - The resource fork is a bit "far" away from the data
> # fork. (myfile/data and myfile/resource are indeed closer)
>
> Well.. kinda tar-copyable. This only holds true if you either a) tar up
> the whole directory, or b) know the fork is there.
>
> cp and similar still loose the fork, and it doesn't hide it from the user
> if you want to move the file.. having a nice, well-defined interface for
> this (along with a necessary stat() bit), would make things easier,
> IM(V)HO.
ehhhm, mv would call "rename" if on the same filesystem, which would
also move the resource forks... ?? Yes, mv would need to know about
the resource fork when it starts copying the whole file for a
cross-filesystem move.
Roger.
-- ** R.E.Wolff@BitWizard.nl ** http://www.BitWizard.nl/ ** +31-15-2137555 ** *-- BitWizard writes Linux device drivers for any device you may have! --* * Common sense is the collection of * ****** prejudices acquired by age eighteen. -- Albert Einstein ********- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Tue Aug 15 2000 - 21:00:30 EST