Subject: Re: Modification Dates in netatalk and samba
From: Bob Rogers (rogers-netatalk@rgrjr.dyndns.org)
Date: Wed Oct 11 2000 - 12:56:34 EDT
From: Jan Dockx <Jan.Dockx@cs.kuleuven.ac.be>
Date: Wed, 11 Oct 2000 10:23:26 +0200
Thanks.
Seems to me netatalk is the one at fault, not samba. When serving
files, netatalk should be more intelligent. It should strip the entry
descriptor 8 you talk about from the resource, and transmit the file
system time stamps instead . . .
High time I got some time to program some things for netatalk :~$
. . .
Jan Dockx
If a rationalization of the way netatalk deals with timestamping is in
prospect, I would like to add the following request.
When I copy folders in the Finder from a Mac local disk to a netatalk
share (using afp/tcp, btw), the Finder (apparently) dutifully sets the
file modification date to that of the original Mac file, so that "ls -l"
on the Linux box shows the original file date, as you would expect.
However, the .AppleDouble file always keeps the current date, and
therefore looks much more recently modified than the data fork file. It
seems to me that, when told to set the modification date for a file,
afpd should also set the .AppleDouble mod date as well.
I suppose this is a rather nitpicky detail (I confess I am embarassed
to explain why I care), but since changing both dates is reasonable,
consistent, and useful (to me, at least), I thought I should pipe up.
Comments?
-- Bob Rogers
This archive was generated by hypermail 2b28 : Wed Jan 17 2001 - 14:32:22 EST