I’m planning on designing a new filesystem over the break. I want a portable example I can use to illustrate implementation details.

It has to be dead simple, run in userland, and be virtualized. I’m thinking of making them be file based.

Anyway, since there are too many acronyms for filesystems, my first thought was on what to call it: npfs

  • non-production filesystem
  • network parallel filesystem
  • not-pretty filesystem
  • nasty|neat python filesystem
  • near perfect filesystem
  • non-profit filesystem

Believe me, the name is the hardest part!