Re: ESXi 3.5 Failing While Creating custom OEM.tgz
For question 1, if you don't have a simple.map/ pci.ids file, ESXi will still have other copies so you should be fine. Not sure if the script will generate an error though.
I haven't used rsync so I can't help with question 2. Check over at communities.vmware.com as the utility has been discussed there.
Question 3 - once you have your install complete, you can modify the oem.tgz directly on the host. You would
1) extract the file to a tmp folder
2) make your changes
3) tar it up again and replace the original. See the customizing oem.tgz article on the home page for steps.
thanks what about this part?
I've recently come upon this site during my vmware esxi research and found the script to compile custom oem.tgz's. While trying to create a custom esxi 3.5 iso I ran into this error during the scripts execution. It asks me if I want to include wget, rsync, ssh, etc and I press Y . It goes through the downloading etc and then it gets to a line that says"
Replacing ^#ftp with ftp in /iso3.5/inetd.conf? [FAIL]
the script failed for some reason, if you can't solve it make a post on the vm-help.com forum.
I have verified that this inetd.conf file is present in the directory, I have the mkesxiaio_4.3.1.sh script and the VMware-VMvisor-InstallerCD-3.5.0_Update_5-207095.i386.iso all within the same folder along with the SSH_FTP_oem_1.1.tgz file. I'm running Debian 5.0 lenny from a virtual machine.