It appears that this blog has caught the attention of the DragonFlyBSD digest... Which is all fine and good except that this project is just a bunch of non-working code so far. Sorry guys, it's vapor right now!
Right now, I am thinking of how to simulate OS/2's legacy 16bit APIs without actually needing any 16bit code - although I don't intend to support any 16bit code segments, so all IOPL stuff won't work but things which used ioctls like Holger Veit's fastio$ may be supported. (isn't it silly that IBM never followed through and introduced the 32bit clean console APIs - MOU/KBD/VIO - from their aborted OS/2 PowerPC project but they did port GRADD).
Anyways, back on topic - for anyone reading this - there is no working code yet. Once I have something to show, I'll provide a link to a website where the code will be published. I plan to use a BSD style license.

I have been thinking... Now that DragonFlyBSD 1.8 was released today, if I use the MAP_VPAGETABLE facility, I have no immediate need for any in-kernel code. I could simply rely on that for an initial implementation.
Or, I can just leverage DragonFly's VKERNEL to accelerate development.

Well, that has pretty much made up my mind: Matthew Dillon has nearly completed his VKERNEL for DragonflyBSD. Having that available would also be good to accelerate the development of WarpBSD.

No new work done but the DragonflyBSD project has been doing some pretty interesting stuff. However, I still think I should base the work on FreeBSD 4 and develop a more OS/2-alike IFS system instead of the VFS which BSD has.