Well I have rebuilt it in a ubuntu (jaunty) image. I've created a "build" script now that does 99% of the initial configuration, if people decide they want to create their own "image" from scratch for VPC they can create and image and then run the script it and it should setup and fix the majority of the issues with VPC and help set the image up for development.

The best news is so far I haven't see ANY lockups!!! It so far has been stable and I haven't had to work around the OS like I had to in a couple places in Debian.

Second I was able to get the screen resolution to be 1280x1024 which makes it a lot larger than the 800x600 it had wanted to use. If you have a smaller monitor; you can change the resolution down to 1024x800 or smaller in the gnome "display" control panel.

I'm pretty happy with this version. I have only a couple more tests and then I should be able to release it. (Hopefully in the next couple hours)

The first image I upload will probably be < 1 gig. It will be the full OS, and all the install scripts to install scratchbox, nokia's binaries, qt, python, etc... Once that is up; I will make a "second" image that will have scratchbox installed. That image probably will be around 2.5 gigs.

The only difference between them, will be that scratchbox & nokia sdk will be installed in one, and not the other. In the one that doesn't have Scratchbox/sdk it will have a script which will set it all up for you. You just need a decent internet connection so that it can download the stuff it needs.

In EITHER image; you will still need to run the script that will download and install the Nokia Binaries, and then optionally the scripts to install the Full QT (including creator) and Python if you want either of them.

For those who are interested I have been committing my entire scripts directory to the projects SVN, and the images have full svn support and several of the scripts have built in to them to do a svn update on the full "Maemo_Install" folder so that no matter "when" you download the image; it should be able "maintain" itself -- eliminating the need for me (or anyone else) to have to regenerate the full os images or manually update them.

I know on some of the scripts their is probably a better method to do it -- but I took the "simple" way. ;-)

Despite being a huge proponent of security -- since this image really is designed for one use (developing) I have also "enabled" the root account so "su -" will work. The root users password is "root" The normal user is "maemo" with the password "maemo". The image auto-logs you in. No reason to "get" in your way while developing.

Nathan.