Originally posted by: scottws
Originally posted by: Brazen
I've used it on PIII 800mhz boxen with 512 meg of RAM. As far as I can tell, when installed on linux, I can't tell a difference between installing the system inside VMWare or installing it on top of bare metal. On Windows though, it does not run nearly as fast. Of course on linux I use a minimal install with all the services disabled except what is necessary. The base system with VMWare does use up about 80-100 meg of RAM, so you'll want to expect your guest OS (the OS inside VMWare) to be unable to use that much of your RAM.
What I'd like to do is sort of two-fold. I don't know how practical it really is, but it won't hurt anything to try.
I want to set up the aforementioned HP box as a Debian VMWare server. Right now, I just want a single virtualized Samba file server. I'll probably go Debian there as well.
I like Debian because apt-get is my favorite package manager. I don't like Red Hat stuff because I had real bad experiences with RPM and dependency issues when I played around with Red Hat 9 and FC2. I might do SuSE as well, but I don't really know what YAST is like at all.
In any case, obviously you might want to ask, "Why don't use just use the real box as the Samba file server?" The answer is that I'm basically playing around with virtualized servers and a file server at the same time, and therefore why not?
The thing here is that I'm not a Linux guru. At all. I've played around with it in the past, but I've never really had what I would consider a "successful experience" with it. But that's because of my ATi videocard and Broadcom-based wireless card. The HP has neither of these.
Now, what sort of services are necessary on the real machine to allow the VMWare-ed Samba file server to work on the network? What can I choose to not install?