>> Martin, do you *really* need to keep the completely the same codebase for
>> kernel and userland?
>
> Well, yes. There are also BeOS and other ports of the driver, and I'd
> like to stay them close.
BeOS is not popular, not Open Source, and not the OEM OS for special
hardware like Sun and SGI produce. In other words, it is a dead-end OS.
Other ports can use a podfuk-enhanced NFS server AFAIK.
Look at ext2. Linux code, BSD code, and userspace code all exist.
The userspace code is part of a library that all the ext2 tools use.
By keeping the source unified, you cause yourself many problems.
It is harder for normal kernel hackers to help you, since your
code does not look like every other filesystem. You might never get
the performance of a normal native driver.
