Subject: AppleDouble/Resource Forks....
From: Harry Zink/Netatalk List (netatalk@fizbin.com)
Date: Tue Aug 22 2000 - 05:08:12 EDT
I was thinking about the resource fork situation on the Mac, and the
apparent need for AppleDouble directories on netatalk - or is there?
While I understand that there is a need to store the resource information
somewhere, why not find a way to store said information in the actual file,
instead of storing it in a separate directory.
Thus, each file could have a header which provides pointers to data and
resource 'fork', and the location they are stored - yet the file itself is
stored in the fs as a single file.
Thus, you'd have:
+--------+-----------------+---------------------+
<| header | xx data fork xx | ** resource fork ** |>
+--------+-----------------+---------------------+
Location of data/resource fork could be specified by either byte offset, or
actual location on the disk (the latter would make it easier to update
changing sizes of either).
The big benefit of it all is that if another network system, like Samba,
deletes a file, no other strangglers of that file need to be cleaned up -
furthermore, there is no need to manage lots of extra files in lots of
duplicated locations - which should make responsiveness and administration
far easier.
Of course, I'm sure I overlooked something - so, what are the drawbacks to
this suggestion?
Harry
-- CAN'T SEE MAC IN CHOOSER UNDER RedHat 6.2: If you get errors starting AppleTalk under RedHat 6.2 and Mandrake 7.1, you need to manually add "alias net-pf-5 appletalk" to your /etc/conf.modules file.
This archive was generated by hypermail 2b28 : Wed Jan 17 2001 - 14:32:02 EST