I consider this bug fix-released at this point. Builds at http://uec-images.ubuntu.com/karmic/ are now 2G filesystem images. Their sizes are (20091012):
182M karmic-uec-amd64.tar.gz
173M karmic-uec-i386.tar.gz
That is down from a 10G filesystem with download sizes of (20091007):
602M ubuntu-uec-karmic-amd64.img.gz
592M ubuntu-uec-karmic-i386.img.gz
The resize-uec-image tool can resize those with basically no ill effects.
The only applicable change to vm-builder that isn't in the karmic-packaged version is:
1. run apt-get clean
2. change ec2 image sizes from 10G to 2G
I consider this bug fix-released at this point. Builds at http:// uec-images. ubuntu. com/karmic/ are now 2G filesystem images. Their sizes are (20091012): uec-amd64. tar.gz uec-i386. tar.gz
182M karmic-
173M karmic-
That is down from a 10G filesystem with download sizes of (20091007): uec-karmic- amd64.img. gz uec-karmic- i386.img. gz
602M ubuntu-
592M ubuntu-
The resize-uec-image tool can resize those with basically no ill effects.
The only applicable change to vm-builder that isn't in the karmic-packaged version is:
1. run apt-get clean
2. change ec2 image sizes from 10G to 2G