At 4:40 PM -0600 2/5/03, pkeidesis wrote:
I know very little about it from the Unix point of view, but from
the Mac point of view -- not all files have resource forks worth a
tinker's damn. If rsrc is zero, well, then it is zero. pure ascii
files are like that.
otoh, things like icons are mostly all rsrc.
Understood. I should probably explain that I'm putting together a
"Metadata" tab for Morinfo (a file system browser). So, I get to
look into a number of odd corners and try to unearth plausible
explanations, useful references, etc.
Actually, it may well be a moot point. Not that many files are
sparse, so the number of bytes is a reasonable indication of the
number of blocks. It's just that I'd rather have the individual
block count for each fork.
BTW, I'd be happy to see a bit more information about ..namedfork.
Google only found a few references, including "Inside Mac OS X:
Performance", which says:
Although Apple recommends moving resources into data files in the
application package Resources directory, it is possible to access
the resource fork of a file on an HFS Plus volume by adding the
suffix:/..namedfork/rsrc to the end of the file pathname. Because
this doesn't work on other file systems, notably UFS, and because
it requires you to parse the resource fork structure directly,
this technique is not recommended.
My interest is that I'd like to think about storing metadata with
files. I think I need to take a closer look at the relevant modules.
I knew Chris had been porting some of Matthias's MacPerl libraries
over to OSX; looks like I may get a chance to use some of them...
-r
--
email: [EMAIL PROTECTED]; phone: +1 650-873-7841
http://www.cfcl.com/rdm - my home page, resume, etc.
http://www.cfcl.com/Meta - The FreeBSD Browser, Meta Project, etc.
http://www.ptf.com/dossier - Prime Time Freeware's DOSSIER series
http://www.ptf.com/tdc - Prime Time Freeware's Darwin Collection
