Ok, I looked at it, and it seems it's really the msdos fs tricking the
ramdisk away, since it sets the blocksize to a different value, and this
operation clears the ramdisk [It happened to me during development]...
Now, the real solution would be to remove this feature from the ramdisk,
but this is not a trivial work, so do anyone have objections moving
the check for romfs before the msdos-like filesystems?
Janos