Out of the box, I install Ubuntu 6.06.1 LTS Server and ran into some problems. The install.sh did not comment out one of the two lines in there that pointed to the cdrom repository. That took me a little bit to find but once I found it I got a complete install. However, on this installation it would not pass 'ready for virtualmin' tests until I removed the proftpd subfolder from etc for it's conf file.
This install had all servers stuck on using the php.ini file under apache2 and only version 5 would work. None of the php switching would function.
I then started fresh again and modified my own sources.list and commented out the cdrom myself and uncommented everything else including the backports. This time the install.sh worked right out of the box and the system passed the virtualmin ready tests without any other modifications. I did have to go in and turn off the item in dovecot that disallows plaintext auth if not SSL (which would be necessary for just about all of the Outlook/Outlook Express normal users out there).
I had a few other items that I installed initially on the first portland server that I kept and added to this one initially. They were needed for Gallery2 which Bryan runs. I do the following after installation...
apt-get -y install libgd2 php4-gd libapache2-mod-php4 netpbm imagemagick jhead zip unzip
ln -sfn /etc/apache2/mods-available/rewrite.load /etc/apache2/mods-enabled/
My php version is still stuck and I can't seem to affect any change in that from the toggles in Virtualmin and it's stuck on version 4 this time.
My initial notes can be found in a comment to bugtracker #2990 that kinda sorta seemed relevant and was still open.
Suffice it to say that I'll probably need you to come into the box and look around/fix it so that the php switching all works again. I'd like to know what you do to fix that too as I will be building another backup server on identical hardware for backing up our web services at another yet to be determined datacenter.
I sent basically this same text in an email to Joe directly about 3 days ago and that message includes the credentials to access this new server as well as our old one if you wanna poke around in it and see what the problems are there.
Suffice it to say that we are teetering on the edge of a cliff here and the quicker I can get this new server at 100% and swapped into service the better I'll feel. :-)
Thanks guys!