Nathan Vander Wilt

Yes, it looks like they do use one of this libraries structs directly to format the volume from xo-server itself, and set the VolLab in the boot header. The summary...

Actually, correction: The `FREG` flag fatfs/struts.js corresponds to `S_IFREG` in . That is, it indicates that the entry is a "regular" file and so it is usually already set for...

@julien-f Sorry been busy with other projects and I have to admit I'm myself rusty on the details of this library. Basically you would need to do something like what...

Taking a step back: I suspect it would be helpful to add a public "format volume" helper method that does everything needed here? That doesn't totally solve the general case...

Interesting, thanks for the tip! I've created a cross-reference from the issue #5 (right now this library only every writes to the first table _at all_ :crying_cat_face:) as transaction safety...

To summarize/paraphrase the linked article: TFAT works by using the second FAT as the main "workspace" and then directly copying that to the first table at the end of a...

To be honest, I've been really _dis_inclined to correct this given the performance problems we're already having on Tessel. However, "double bookkeeping" here may not add quite as much overhead...

See also https://github.com/natevw/fatfs/issues/19 for another reason (and presumably guide the approach) to do this.

Script updated for on-device testing too: ``` var fs = null, data = Buffer(512*1024); if (0) { var vol = require("./img_volume.js").createDriverSync("/Users/natevw/Desktop/fat32.img"), fs = require("./").createFileSystem(vol, {umask:0020, uid:99, gid:42}); writeData(); } else...

Couple notes: - sdcard is currently dependent on fatfs@^0.9.5 which predates a bunch of caching fixes/improvements! - with latest version, I see a slowdown as the number of files grows,...