On Mar 9, 2011, at 1:59 PM, Scott Ribe wrote:

> On Mar 9, 2011, at 11:19 AM, Dan Shoop wrote:
> 
>>> 
>>> And most frequently what's not restored correct is File Security 
>>> Information - the consequences of which I don't know. And then also 
>>> Attributes. A huge percentage of small system help and programs (the small 
>>> BSD programs) are not stored anymore in the data fork. Apple is compressing 
>>> them, and putting them in the Attribute File,
>> 
>> Um... no, not actually accurate. It's just using a named resource fork of 
>> the file for storage. 
>> 
>>> a component of HFS just like the Catalog File.
>> 
>> No, incorrect. No file data goes in any of the filesystem catalogs or 
>> b-trees, all file data is stored in the file, though "file" here will 
>> include [old style] resource forks and other named forks. 
>> 
>>> So these files take up zero sectors on disk since they are stored in the 
>>> Attribute File.
>> 
>> Again, no. 
> 
> Actually, he's right. In 10.6 the content of very small files are stuffed 
> into the HFS attributes file. They're referred to as "named forks", but 
> they're stored inline with attributes, and do not have any blocks allocated 
> for data storage. Many system files too large to be stored as an attribute in 
> the attributes file do have their compressed content stored in a resource 
> fork, which does have a distinct allocation of blocks for its storage--and I 
> guess that's what you're thinking of.

You're saying the same thing. There are no resource forks any more. All forks 
are now named named. Compressed files have the data fork empty and the 
compressed fork stores the data (in compressed form.) Depending on the size of 
the named fork it may be stored together with other other named forks - 
commonly together with file attribute forks - or it can be stored separately, 
this has always been true for named forks under HFS+. File sizes measure data 
forks in HFS+ filesystems. Compressed files have no data fork size. A file 
consists of a single data form and zero or more named forks. No data (only 
unless it's compressed, in which case it's not the data anymore) is stored in 
named forks. 

-d

------------------------------------------------------------------------
Dan Shoop
[email protected]
GoogleVoice: 1-646-402-5293
aim: iWiring
twitter: @colonelmode



_______________________________________________
MacOSX-admin mailing list
[email protected]
http://www.omnigroup.com/mailman/listinfo/macosx-admin

Reply via email to