Tag: vmufat
-
A pleasingly retro look and feel
I have done almost all my development of Hexxed on a Macbook, but have now updated the git repo on my Linux laptop and run it there – some interesting differences: the Linux app has a pleasingly retro look and feel to it – no anti-aliased fonts here on Linux key reptitition works as expected…
-
New version of mkfs.vmufat available
I have posted a new version of mkfs.vmufat, a tool to make a VMUFAT filesystem, at my GitHub repo: it will now format a file as VMUFAT volume (if you use the -f switch). Would love to hear your feedback – my posting of the source code for the filesystem itself generated a bit of…
-
Mild roasting delivered
Well, I didn’t get the worst-of-ever kickings from my posting to LKML, and I did get some pointers as to how to improve the VMUFAT code, which I am now working on amidst anything else I am doing in my life.
-
Spoke too soon (of course)
It’s like the curse of the software demonstration: it doesn’t break until then. I discovered as soon as I posted that I was ready to (try to) push the VMUFAT stuff up to main line that there was a bug in the software. Very large VMUFAT volumes were not being properly handled. But I think…
-
Taking down the bug
Finally nailed the bug in my readdir function. The code was stuck in an endless loop because it did not return an empty dirent when it reached the end of the directory – instead returning the list of files in the directory over and over again. To fix this I made sure that any following…
-
A question for a C guru
The debugging continues, but unfortunately I have not yet been able to identify what is fundamentally broken with my file system code. But along the way I have spotted and fixed various bugs. Here is one, I am not even sure why it compiled in the first place, so maybe a C guru could tell…
-
Filesystem works
Not much of a surprise really, as the old code worked too, but the updated VMUFAT filesystem code works with 3.2.0-rc7. Just have to clean it up so it is of an acceptable standard. Update: In the unlikely event that someone is testing the code I should warn you that the above was overly optimistic.…