Re: AppleDouble/Resource Forks....


Subject: Re: AppleDouble/Resource Forks....
From: Rasca Gmelch (rasca@triad.de)
Date: Wed Aug 23 2000 - 13:15:25 EDT


hi harry,

Harry Zink/Netatalk List wrote:
>
> on 8/22/00 2:18 AM, Rasca Gmelch at rasca@triad.de wrote:
>
> > and then you can't access the files in the normal way under the
> > unix/linux system - i mean the data fork! :-(
>
> Okay, so such a header would interfere with a standard *nix reading these
> files. While this is irrelevant for application files, since they are of no
> use natively anyways, this could be a slight issue with data files (again,
> if you are using the device uniquely and solely as an appltealk file server,
> I don't see much need to ever need to 'use' the files in the traditional
> way. Only way I can see is to natively copy a file, in which the single file
> format again would be of benefit.

we use netatalk in a mixured network (linux,nt,macos).. so the file
itself doesn't have more than the data fork it self.

> Now, I understand that the header, thus, is bad - how about just placing
> this information at the very end of the file? That way, no garbage at the
> end; the fs knows where the end of the file is, netatalk could just look
> there, in a designated place, and grab the same information.
>
> Any drawbacks to that?

i don't see more drawbacks to stay on the current solution with
the .AppleDouble files.. i would improve the server / daemon
software and wouldn't change the current concept. here we
would loose time to find a stable solution.. imho.

cu
 rasca

-- 
Triad Berlin Projektgesellschaft mbH * Marburger Str. 3 * D-10789 Berlin
Fon +49 (0)30 219098-69 * Fax +49 (0)30 219098-61 * http://www.triad.de/
.____________/\ Triad Berlin: Culture Media Environment /\_____________.



This archive was generated by hypermail 2b28 : Wed Jan 17 2001 - 14:32:04 EST