Developers corner

This page is for developers who are interested in working on umlwin32. This page is in no way complete and I will keep updating as I think of things to put. It you want to work on any of these or anything else related to umlwin32 drop me a note at ckudige "at" users dot sourceforge dot net or post a message in uml-devel mailing list.

Tasks in progress

  • Implementing signal support.

  • Testing bash, ksh, simple commands like tar/gzip etc

  • Optimise ubd block access which is quite slow on windows.

  • Implement win32 mmap() and unmap() on 4K boundaries: This is the biggest stumbling block. I havent had much luck with this. Standard win32 APIs (MapViewOfSection, etc.) work on 64K boundaries. The same seems to be true for native APIs too (NtMapViewOfSection and ZwMapViewOfSection).

    Funnily, I see that we can map at 4K boundaries with the physical memory device (\Devices\PhysicalMemory). This might be the clue we need to follow for fixing this problem.

Short-term tasks

  • An important task - To create a platform dependant layer and move win32 specific things out there. Make sure that the code compile for both Linux and Windows properly.

  • Test/debug as many system calls as possible. We can use Python for this.

  • Create a boot-disk with init/getty/login etc.

  • Merge with the latest UML patch so that we are up-to-date.

  • Move over to win32 API instead of Cygwin API. This should make things cleaner and faster.

  • There are a lot of limitations outlined in the Technical Details page. Eventually we need to overcome these limitations and implement them more optimally.