Re: Is there a file system flag for >2GB file support?
Re: Is there a file system flag for >2GB file support?
- Subject: Re: Is there a file system flag for >2GB file support?
- From: Quinn <email@hidden>
- Date: Thu, 13 May 2004 17:21:22 +0100
At 15:53 +1000 11/5/04, Sam Vaughan wrote:
If FCP were testing the bSupports2TBFiles bit, which VOP/VFS
interface would the Carbon File Manager be using to ask us the
answer?
AFAIK that would be a new API.
I'd like to put the code in now so that it will all just work when
FCP/CFM are fixed.
As a rule I recommend against that approach. I could swear that DTS
published a Q&A entitled "Test what you ship" that explains why this
is a bad idea, but I can't, for the life of me, find it.
At 11:54 -0500 11/5/04, Brian Bergstrand wrote:
How about an extension to getattrlist()? Another VOL_CAP?
Perhaps VOL_CAP_FMT_LARGE_FILES?
Well, I'd prefer a new attribute that returns the maximum file size
for the file system, that way file systems can be specific about what
they support.
I'd also like to see getattrlist() extended so the FS UUID can be
accessed.
Indeed. Please file a bug requesting this and send me the bug number.
<
http://developer.apple.com/bugreporter/>
Note that we already have a mechanism for associating volumes with
64-bit unique identifiers (vsdbutil) but there's no nice way for the
volume format to get involved in the process.
S+E
--
Quinn "The Eskimo!" <
http://www.apple.com/developer/>
Apple Developer Technical Support * Networking, Communications, Hardware
_______________________________________________
darwin-kernel mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/darwin-kernel
Do not post admin requests to the list. They will be ignored.