I would think even a UFS filesystem could emulate
that.
Where would you hide the creator attributes? Or, are you
uggesting a kludge workaround (e.g., change the "extension"
to something unique; build some middleware that consults
a user-maintained table of creator attributes; etc.)?
I haven't looked into this because my Macs all use HFS+, so I don't know how
Mac OS X emulates resource forks on a UFS filesystem (perhaps Zane or Doc do).
However, when storing Mac files on, say, a FAT volume, a hidden folder is
made to hold the additional data in the resource fork. This includes
type/creator information.
Ah, OK. So the OS already has provisions to handle it and
hides those details from the user. I.e. it does the things
I was insinuating the user would have to do, manually.