Fix resource link
Remove last packer script standing

If this is owned by a different user than the user running the *next*
provisioner, it'll fail.  Yes, Packer should clean these up.
AMI provisioner doesn't support SSH password

WTF.  So the only way to auth to an instance is with an ssh key.

Also adding the ec2-user to the wheel group, as this is the group that
generally gets the sudo privileges.  The group has to be set before
the user logs in, or it won't be in effect for that login session.

Conflicts:
	packer.json
Fine-tuning Amazon AMI

Ensure /dev/sd* are symlinks to appropriate devices, so they match
what you feed into the AWS APIs.  Mounts first ephemeral disk at
/media/ephemeral0 to match Bashton AMIs.
Script normalization and cleanup

Conflicts:
	packer.json
Ensure ~ec2-user/.ssh exists
Use `git describe` in artifact names

Conflicts:
	packer.json
cloud-init really is a pain in the ass
Create ec2-user via cloud-init only
Force cloud-init to run again

cloud-init runs once when Packer creates an instance from the base
AMI.  Need to wipe that out to force it to run again for the final
images.
Moar tagz

Conflicts:
	packer.json
Don't expect ec2-user to exist

In fact, it *shouldn't* exist for Vagrant instances
Attempt to make the Vagrantfile referential to the project
curl -L needed for raw.github.com redirect handling
image_name as a parameter added as well as amazon-hvm.cfg kickstart config to add specific hvm-required bootloader flags
amazon-vm.cfg renamed to amazon-hvm.cfg
040-cleanup.sh now nukes all of /tmp/*, just to be safe
42!

Yes, the answer.  The answer to the ultimate question of life, the
universe, and how do you resize a fucking root partition on boot!
Merge pull request #1 from blalor/sharing_upstream

Sharing upstream