Nick Bastin wrote:
>
> Since it seems that all of the mail I sent this weekend got eaten by the
> corporate mail server, I thought I'd send this again.
>
> If anyone can provide me with the necessary information, or at least some
> of it, I would like to put together a TODO for plex86. This would be
> especially useful to new developers wondering what needs to be worked on,
> as well as some milestones for existing developers to work towards. Given
> that this kind of document is usually at the top of the source tree, it
> slightly blurs the line between what belongs in the docs tree and what
> belongs in the source tree, but we'll sort that out at a later date.
This is a good idea. Lot's of people have been emailing
me asking what they can do to help. A todo list would
be very helpful for this. I offer the following entries
to begin with.
- Rework the GUI code, to use pull downs menus, separate
configuration windows etc. Before starting this, poll this
developer's list to find out what toolkits to use.
- Write an disk write cache interface, such that a user can
begin a VM session at a known disk image/partition state,
and store disk block writes thereafter, into some kind of cache/file.
Disk accesses therefore have to hit the disk cache first. If
a read is not satisfied, then pass through to the image
file or partition. Allow the user (through the GUI) to
commit the changes, if they have 'writer' access. Otherwise
we just dump the write cache upon exit. This interface has
to support multiple VM accessing the virtual disk, only
up to one which has 'writer' access.
(We don't yet have disk emulation in the VM. You could
work on this independently though. Assume you will get
reads/writes of N block quantities @ 512bytes per block)
