Subject: Re: [netatalk-admins] Re: Yet Another Netatalk problem (YANP)
From: a sun (asun@zoology.washington.edu)
Date: Thu Aug 21 1997 - 09:48:51 EDT
Question: Why does netatalk insist on creating the Finder Info for Unix
files (e.g., files that were created on the server, not by a Mac OS
client)? I could see this as a caching mechanism to avoid having to
synthesize the Finder Info each time, but netatalk should not _require_
the presence of the Finder Info in the .AppleDouble directory to function
properly.
netatalk doesn't and really shouldn't have any idea of what the finder
info should be. it's only supposed to save it and not fiddle with
it. for read-write volumes, this works out okay. when asked about a
file w/out a corresponding .AppleDouble entry, netatalk sends a bogus
finder info entry and the mac client comes back w/ a fixup reply.
on read-only volumes, this is going to be difficult to solve for the
general case as the fixup gets rejected. however, i should be able to
peek in the os8 technote and modify the default finder info reply so
that it works. ugh.
-a
This archive was generated by hypermail 2b28 : Sat Dec 18 1999 - 16:26:14 EST