Date: Wed, 24 Nov 2004 20:50:39 -0800 From: "David Schwartz" <davids@webmaster.com> To: <freebsd-chat@freebsd.org> Subject: RE: VMWare Message-ID: <MDEHLPKNGKAHNMBLJOLKGENFAAAB.davids@webmaster.com> In-Reply-To: <1101342070.1100.39.camel@chaucer>
next in thread | previous in thread | raw e-mail | index | archive | help
> I didn't get a very good answer to my question about whether it was > worth using if all the client operating systems were FreeBSD or Linux. It depends what you're doing. > For these (much better) OSs, reboots are very rarely needed. The OS > provides all the facilities required for protecting applications from > one another, and sharing resources between applications in a reasonable > way. This is not really true. You cannot easily create the illusion of multiple machines with their own rules, users, and networking setup. The resource sharing always runs into problems. If you share by processes, for example, whoever makes more processes gets more CPU. > It is easy to kill runaway applications. So would there be much > point in running VMWare with several guest copies of FreeBSD? Maybe not, again, it depends what you're doing. What happens when the next person you want to let use the machine really needs Linux for some reason? What happens when person needs to be able to customize the kernel? Or needs a special network filtering module? Vmware lets you do a lot of things that are difficult to impossible to do any other way. If you don't need any of these things, you don't need Vmware. It's certainly great for a desktop when you need to support a large number of different operating systems. It's great for kernel development, where a crash can be debugged from one vm to another without hosing your editor session working on the code. DS
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?MDEHLPKNGKAHNMBLJOLKGENFAAAB.davids>