Issues with installation on mac 10.5 and possible typos/fixes

using:
mac 10.5
ruby 1.9.2-p290
vagrant 0.9.4

on first run-through of vagrant up:

There is a syntax error in the following Vagrantfile. The syntax error
message is reproduced below for convenience:

/Users/kramer/Sites/projects/drupal/aegir-up/Vagrantfile:44: syntax error, unexpected tLABEL
    config.vm.define "#{Hs:Shortname}#{index}" do |hs_config|

Fixed by changing:
#{Hs:Shortname} to #{Hs::Shortname}

on second run of vagrant up:

/Users/kramer/.rvm/rubies/ruby-1.9.2-p290/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:36:in `require': no such file to load -- settings (LoadError)
	from /Users/kramer/.rvm/rubies/ruby-1.9.2-p290/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
	from /Users/kramer/Sites/projects/drupal/aegir-up/Vagrantfile:2:in `block in <top (required)>'
	from /Users/kramer/.rvm/gems/ruby-1.9.2-p290/gems/vagrant-0.9.4/lib/vagrant/config/loader.rb:83:in `call'
	from /Users/kramer/.rvm/gems/ruby-1.9.2-p290/gems/vagrant-0.9.4/lib/vagrant/config/loader.rb:83:in `block (2 levels) in load'
	from /Users/kramer/.rvm/gems/ruby-1.9.2-p290/gems/vagrant-0.9.4/lib/vagrant/config/loader.rb:79:in `each'
	from /Users/kramer/.rvm/gems/ruby-1.9.2-p290/gems/vagrant-0.9.4/lib/vagrant/config/loader.rb:79:in `block in load'
	from /Users/kramer/.rvm/gems/ruby-1.9.2-p290/gems/vagrant-0.9.4/lib/vagrant/config/loader.rb:76:in `each'
	from /Users/kramer/.rvm/gems/ruby-1.9.2-p290/gems/vagrant-0.9.4/lib/vagrant/config/loader.rb:76:in `load'
	from /Users/kramer/.rvm/gems/ruby-1.9.2-p290/gems/vagrant-0.9.4/lib/vagrant/environment.rb:376:in `block in load_config!'
	from /Users/kramer/.rvm/gems/ruby-1.9.2-p290/gems/vagrant-0.9.4/lib/vagrant/environment.rb:381:in `call'
	from /Users/kramer/.rvm/gems/ruby-1.9.2-p290/gems/vagrant-0.9.4/lib/vagrant/environment.rb:381:in `load_config!'
	from /Users/kramer/.rvm/gems/ruby-1.9.2-p290/gems/vagrant-0.9.4/lib/vagrant/environment.rb:316:in `load!'
	from /Users/kramer/.rvm/gems/ruby-1.9.2-p290/gems/vagrant-0.9.4/bin/vagrant:40:in `<top (required)>'
	from /Users/kramer/.rvm/gems/ruby-1.9.2-p290/bin/vagrant:19:in `load'
	from /Users/kramer/.rvm/gems/ruby-1.9.2-p290/bin/vagrant:19:in `<main>'

fixed by changing:
require "settings" to require "./settings" in the Vagrantfile.

On third run of vagrant up:
Things are looking good and the box download is successful.

Then this happens and I'm pretty stumped since this is my first attempt at using puppet with vagrant:
but maybe this isn't an error?

[hm] Running Puppet with /tmp/vagrant-puppet/manifests/hm.pp...
stdin: is not a tty
notice: Scope(Class[main]): 
Running Puppet manifests to install and/or update Aegir.

        This may take awhile, so please be patient.
        For more detail on the operations being run, edit settings.rb,
        and set 'verbose = 1'.

notice: /Stage[main]/Aegir::Apt/Apt::Keys::Key[aegir]/Exec[apt_key_add_aegir]: Triggered 'refresh' from 1 events

notice: /Stage[main]/Apt/Exec[/usr/bin/apt-get update]: Triggered 'refresh' from 6 events

notice: Finished catalog run in 48.84 seconds

I went ahead and ran vagrant ssh to check stuff out.
Tried accessing aegir at 192.168.32.10 and got the apache 404.

I noticed the postinstall.sh script, read through it and decided it might need to be executed. So I did that. I'm not sure if it was the right thing to do.

I exited the box and ran vagrant reload and got this output:

stdin: is not a tty
notice: Scope(Class[main]): 
Running Puppet manifests to install and/or update Aegir.

        This may take awhile, so please be patient.
        For more detail on the operations being run, edit settings.rb,
        and set 'verbose = 1'.

notice: Finished catalog run in 0.45 seconds

sshed back into the box, ran drush @hostmaster uli, and realized I hadn't set up the aegir.local hostname. i added that and went to aegir.local in the browser and saw the aegir site!

is it weird that the site isn't accessible at 192.168.32.10, but is accessible at aegir.local after adding 192.168.32.10 aegir.local to the hosts file?

at this point it seems like everything is working as expected.