> Here's a good example of why this would be handy: If the capacity of > the file system is not known, and I copy 100G of data to it, only to
"copy" is not a file system operation. "write" is. So are "open" and "create". Your "good example" is not handled at the file system level. It's handled by higher layers (such as the Finder), way above the file system and the kernel levels. The file system does tell you how much space it has remaining, so the layer that's doing the copy would/could check beforehand, etc. Time and again, such questions come up and it appears to me that sometimes people try to decipher how file systems work (or should work) by trial and error. After nearly 40 years of Unix, it's unlikely that one would hit upon something so basic that's missing from the file system/operating system. If you are *developing* a file system, even if using a "really simple API" such as MacFUSE, the fundamentals still apply and it's important to understand how things really work. Therefore, I'd strongly suggest going through the file system section of some operating system text. Amit --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "MacFUSE" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/macfuse?hl=en -~----------~----~----~----~------~----~------~--~---
