Date: Fri, 9 Jul 2010 21:20:45 +0200 From: Iv Ray <pobox@verysmall.org> To: Henrik Hudson <lists@rhavenn.net> Cc: freebsd-questions@freebsd.org Subject: Re: what to do when FreeBSD cannot do something? Message-ID: <28A5B2AD-ABC5-4F93-AFC5-7C0CBCDD69B6@verysmall.org> In-Reply-To: <20100707212453.GA4161@alucard.int.rhavenn.net> References: <6AC0293D-2262-4E5C-9616-516B49664FBF@verysmall.org> <201007071111.o67BBnr5093119@banyan.cs.ait.ac.th> <8F676AEB-5188-4F41-A971-C68293AD54F3@verysmall.org> <20100707212453.GA4161@alucard.int.rhavenn.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 07.07.2010, at 23:24, Henrik Hudson wrote: > One caveat is that ESX / ESXi are very picky about their hardware > and pretty much won't run on anything but server class devices > (mobo, NICs and CPU are the big ones). Yes, I'm aware of that. We have entry level, but ESXi compatible, HP and = IBM servers. > VMware still has their VMware > Server (software) solution, but it's slowly being phased out. Also, > it's against the EULA to use ESXi for commercial / reseller > purposes and ESX isn't cheap. Oh, wasn't aware about the ESXi EULA... will check, thank you. Iv=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?28A5B2AD-ABC5-4F93-AFC5-7C0CBCDD69B6>