as a chroot alternative it should very good. I'm not aware of any way to access the parent machine from the virtual machine.
as a virtual server it might perform well if you give each vmware machine a dedicated partition and load up on memory (if you assign 128mb or whatever to a virtual machine it will always have that memory in use) it certainly is inefficient but it does provide a great way of segmenting services while still using a single piece of hardware. and you could run different OSs if you so desire. and with hardware getting cheaper and faster this idea becomes more and more viable. On Monday 07 January 2002 11:57 am, you wrote: > VMware is a wonderful product. I am also amazed that these days a company > with such a technically hard product, not hardware, to make or support > could get funded. > > That said, I was surprised by their newsletter suggestion this morning: > >TECH TIP OF THE MONTH: > >HOSTING SERVICES ON VIRTUAL MACHINES BEHIND VMWARE NAT > >Our users and staff often discover hints and shortcuts that can > >help you get the most from VMware products. This month, our tech > >tip explains how to configure VMware NAT so that your virtual > >machines can provide network services (such as Web and FTP) on > >your public network. NAT enables guest operating systems to share > >the host operating system IP address(es). ... > >Read more about hosting services on > >virtual machines behind VMware NAT at: > >http://vmware1.m0.net/m/s.asp?HB5170575598X1186076X89440X > > This is not the solution I would choose if I was concerned about > performance. I do wonder how well it might work as a chroot alternative. > > Jerry > ======================================================== > Jerry Asher [EMAIL PROTECTED] > 1678 Shattuck Avenue Suite 161 Tel: (510) 549-2980 > Berkeley, CA 94709 Fax: (877) 311-8688
