http://linux-vserver.org/api.php?action=feedcontributions&user=JustinWick&feedformat=atomLinux-VServer - User contributions [en]2024-03-29T08:48:25ZUser contributionsMediaWiki 1.20.2http://linux-vserver.org/Talk:Usage_ScenariosTalk:Usage Scenarios2007-01-03T22:14:52Z<p>JustinWick: When to use, when not to use?</p>
<hr />
<div>== When not to use VServer ==<br />
<br />
IMHO, it'd be great if this page linked to a page containing situations where VServer is *not* appropriate, so that it isn't misused (especially in a security context). It should be made clear that VServer's incredible efficiency comes at a price and it would be great to help people determine what side of that trade off their situation falls in. - [[User:JustinWick|JustinWick]] 23:14, 3 January 2007 (CET)</div>JustinWickhttp://linux-vserver.org/Talk:OverviewTalk:Overview2007-01-03T21:39:24Z<p>JustinWick: </p>
<hr />
<div>== Emulation = Dynamic Recompilation??? ==<br />
<br />
I'm no expert on this, but why in the world would this article claim that "dynamic compilation" is the same thing as "emulation"? I understand that dynamic compilation is sometimes used in an emulator, as opposed to a run-time interpreter, or a setup that pre-translates the text/data segments of a program before it's run, but the statement "The virtual machine simulates the complete hardware, allowing an unmodified OS for a completely different CPU to be run. This is also known as Dynamic Recompilation" is very misleading, especially for those new to virtualization. I'd suggest the second sentence be changed to "Emulators often use Dynamic Recompilation for efficiency purposes." - [[User:JustinWick|JustinWick]] 22:39, 3 January 2007 (CET)</div>JustinWick