Subject: Re: [netatalk-admins] Re: Yet Another Netatalk problem (YANP)
From: Jay (jco@saratoga.award.com)
Date: Thu Aug 21 1997 - 18:34:00 EDT
>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.
Interesting approach. I would have thought that it would send legitimate
finder info since I'm assuming that netatalk has to synthesize something
halfway reasonable for files mapped by AppleVolumes files.
The current approach also cause problems for Mac OS 8 when a copy is
performed on a file that has no entry in the .AppleDouble directory.
Finder copies don't seem to trigger the creation of finder info in
.AppleDouble. If the entry doesn't already exist, the copy fails with
the usual "file couldn't be found" message.
This archive was generated by hypermail 2b28 : Sat Dec 18 1999 - 16:26:15 EST