Subject: RE: Hidden Files Not Being Copied
From: Vaughn, George (GVaughn@IrwinBF.com)
Date: Thu Jan 18 2001 - 14:29:21 EST
You're both right. Ignore my earlier post as erroneous and full of many bad
things. Apparently, my brain decided to shut off, but my hands kept talking.
Feel free to ignore my posts from now on, as obviously undernourished by
brainpower ;-)
I'm going to bed.
G
-----Original Message-----
From: David R Bosso [mailto:dbosso@ltsc.ucsb.edu]
Sent: Thursday, January 18, 2001 11:19 AM
To: netatalk-admins@umich.edu
Subject: RE: Hidden Files Not Being Copied
--On Thursday, January 18, 2001 10:47 AM -0800 "Vaughn, George"
<GVaughn@IrwinBF.com> wrote:
> Macs don't create files without resource forks. If a file exists on a
> MacOS filesystem (FS), it has a resource fork. If a file is copied to a
> MacOS FS without a resource fork, one is created as soon as MacOS looks
> in the directory (this is why MacOS takes a while for DOS-formatted disk
> contents to appear, it's creating resource forks for the contents of the
> viewed directory).
Woah, I think you're confusing resource forks with Finder information.
Resource forks are _not_ ubiquitous. Maybe you've never tried opening a
file with Resedit that does not have a resouce fork and recieved the
following dialog:
"The file 'filename' has no resource fork. Opening it will add one. Do you
wish to open it?
-David
This archive was generated by hypermail 2b28 : Sun Oct 14 2001 - 03:04:31 EDT