[jaclaz]

I had the same impression, I cannot see how it is different from the tools that allow file splitting (for later archiving on floppies. CD's, DVD's, etc.) that exist since forever, when/if implemented in OS filesystem drivers then it will be more "transparent", but until then it seems to me not different from multi-part archives, such as rar or similar.

If I may it would make more sense (to me at least) to use a directory and have a descriptor file, not entirely unlike multi-part vmdk's are implemented.

[noAnswer]

Using split, cat or rar doesn't allow random access.

[jaclaz]

But also this "extension" doesn't seem like allowing it.

On the contrary (but it is a specific "niche" case) the mentioned vmdk split format allows to mount the vmdk same as monolithic, with full random access.

[noAnswer]

Of course it does. "BigFAT allows random read and write access to any file, even if larger than 4GB, as required by databases."

[jaclaz]

I think we are talking of two different things, I was talking of the extension document/specification, that one seems to bring no particular innovation.

The actual implementation (by SEGGER or by someone else):

>Q: Can I implement BigFAT myself?

>A: Absolutely. BigFAT is a specification made available by SEGGER. Anybody is free to write a piece of software implementing it. No fees, no royalties, no headaches. You do not even have to let SEGGER or anybody else know.

is what may allow that (random access), this implementation would be useful if - instead of a "feature" of a given app/program - it would be implemented as a filesystem driver of sorts.