On Thu, 2009-09-17 at 08:57 +1200, [email protected] wrote:
> On Wed, 16 Sep 2009 18:57:14 +0100, Dan Wallis <[email protected]>
> wrote:
> > 2009/9/16 Aidan Gauland <[email protected]>:
> > Your details are a little sketchy. I understand you're interested in
> > setting up a web server, to have a play around. If that's not right,
> > stop reading now, and let us know what you really meant.
> 
> That's exactly what I want, but a *virtual* server, so I can play with
> it (almost) as if it were a separate machine, and because I want to
> set up more services later (such as SSH) and don't want to make major
> changes to my system.
> 
> --Aidan
That's exactly how I do my development work. I have a low power quad
core server with 4GB memory ( resources like this get important if
you're going to run a few of them ) for this. I don't really recommend
running the following on a single core machine...

vmware server 2
( http://downloads.vmware.com/d/info/datacenter_downloads/vmware_server/2_0 )

use bridged networking. You can either play with your dhcp server to
allocate a "static" ip address to the virtual server's mac address ( my
preference ), or set a static one. The virt server will become, to all
intents and purposes, just another machine on your home network. vmware
has a nifty web based interface to manage and access the servers
directly.

The only problem is that few resources are shared between physical and
virtual machines, so you can get performance degredation all round if
you're not careful. However, 256MB is loads of memory for what you're
after if you're not running a GUI.

Cheers,

Steve
-- 
Steve Holdoway <[email protected]>
http://www.greengecko.co.nz
MSN: [email protected]
GPG Fingerprint = B337 828D 03E1 4F11 CB90  853C C8AB AF04 EF68 52E0

Attachment: signature.asc
Description: This is a digitally signed message part

Reply via email to