> 
> On Tue, Dec 02, 1997 at 08:15:09PM -0800, Time Keeper wrote:
> > A thought to consider: Apple's Hierarchical File System (HFS) has a useful
> > notion: the "resource" fork. The best description I ever heard of it was as
> > "extensible meta-data."
> 
> Sorry, but I think this is one of the worst things on mac. ;-)  When an
> average user (like me) transfers a file from mac to some real computer
> (sorry :), he will soon discover that he can't read the gif/tiff/whatever
> file on other systems because mac has corrupted the file by adding 128
> bytes of garbage in front of it.  I think the Amiga's way was better -
> keeping the Amiga specific information in a separate .info file so the
> data file remained untouched.
> 
> Well, this is Yet Another Religious Issue.. but puh-lease don't force me
> to use mac-like kludges on NetBSD :-(

Jukka,

Your problem is not that the mac keeps a seperate resource fork, but that
you used a file transfer method which was not very savvy. That's not the
OS's fault. :-)

For ftp, I typically use fetch, and the "Raw Data" mode will do exactly
what you expect. Only the data fork, not the resource fork, goes along
for the ride. "Binary" mode actually uses the MacBinary format, which
does add extra data to the front of a file. Note: that data's not the
resource fork, but a combination of the finder info, and some sort of
length info so that the data and resource forks can get split apart later.
If you only get 128 extra bytes, I doubt you actually got a resource fork.

Take care,

Bill