I have started some software engineering to get ready to start coding up my Slack Filesystem. Basically it will be a virtual filesystem meaning that it will reside on top of ext2. I have been told that I should use the term "virtual filesystem" because linux uses this to term to mean a layer of the kernel subsystem that facilitates an interface for other filesystems. What I mean when I use Virtual Filesystem, that in essence or effect is a filesystem but not to the fact that it is formatted on the disk itself. Thus the harddisk or even parts of the harddisk are not formatted. The Slack Filesystem is virtually there.

But I can see confusion with using the same term, so I will create a new one for the Slack Filesystem. Let's say that is a parasitic pseudo-filesystem. Parasitic cause without the slack space of another filesystem it can't exist, and pseudo because it is "apparently similar" to a real filesystem.

On to my point. I will be finishing my 'software engineering' phase of the project and soon be moving into the actually coding. I am taking my time and attempting to think ahead, which the lack of has created problems in past projects.

I still have the issue with the cache incoherency. I will squeeze in some time to figure it out.