<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Virtualization Makes Traditional Operating Systems Obsolete</title>
	<atom:link href="http://www.linux-mag.com/id/7532/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.linux-mag.com/id/7532/</link>
	<description>Open Source, Open Standards</description>
	<lastBuildDate>Sat, 05 Oct 2013 13:48:18 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1</generator>
	<item>
		<title>By: jcalcote</title>
		<link>http://www.linux-mag.com/id/7532/#comment-7023</link>
		<dc:creator>jcalcote</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.linux-mag.com/id/7532/#comment-7023</guid>
		<description>&lt;p&gt;\&quot;And I’m not talking about using some lame marketing ploy by simply renaming everything to make it sound more virtual but actually changing the way those services function to fit into these workload containers.\&quot;&lt;/p&gt;
&lt;p&gt;What does this mean? You\&#039;re spouting non-sense about removing traditional OS\&#039;s. What piece of software will provide the traditional OS services required by all of these \&quot;virtual services\&quot;? *SOME* OS is required underneath it all? If it\&#039;s not a traditional OS, then it will be a new OS, that will in time become YATOS (Yet Another Traditional OS).&lt;/p&gt;
&lt;p&gt;Please explain how you will do away with operating systems, and still provide the services those systems provide today.
&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>\&#8221;And I’m not talking about using some lame marketing ploy by simply renaming everything to make it sound more virtual but actually changing the way those services function to fit into these workload containers.\&#8221;</p>
<p>What does this mean? You\&#8217;re spouting non-sense about removing traditional OS\&#8217;s. What piece of software will provide the traditional OS services required by all of these \&#8221;virtual services\&#8221;? *SOME* OS is required underneath it all? If it\&#8217;s not a traditional OS, then it will be a new OS, that will in time become YATOS (Yet Another Traditional OS).</p>
<p>Please explain how you will do away with operating systems, and still provide the services those systems provide today.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: khess</title>
		<link>http://www.linux-mag.com/id/7532/#comment-7024</link>
		<dc:creator>khess</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.linux-mag.com/id/7532/#comment-7024</guid>
		<description>&lt;p&gt;How does VMware not use an OS with ESXi? We assume that we\&#039;d need an OS because we\&#039;ve been conditioned to think that way. I think there\&#039;s a better way and it isn\&#039;t just using a marketing ploy to do it.
&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>How does VMware not use an OS with ESXi? We assume that we\&#8217;d need an OS because we\&#8217;ve been conditioned to think that way. I think there\&#8217;s a better way and it isn\&#8217;t just using a marketing ploy to do it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jeff_gates</title>
		<link>http://www.linux-mag.com/id/7532/#comment-7025</link>
		<dc:creator>jeff_gates</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.linux-mag.com/id/7532/#comment-7025</guid>
		<description>&lt;p&gt;ESXi is an OS, it is a cut down Linux like OS.
&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>ESXi is an OS, it is a cut down Linux like OS.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dmurphy18</title>
		<link>http://www.linux-mag.com/id/7532/#comment-7026</link>
		<dc:creator>dmurphy18</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.linux-mag.com/id/7532/#comment-7026</guid>
		<description>&lt;p&gt;I think what he is talking about is that all the regular joe user needs is access to the net/cloud and everything is provisioned there.  Hence do we need Win / Linux / etc. to do that, maybe its enough to just get the network connection and browser up, forget the rest.  Of course there shall still be need for OS\&#039;s to do the heavy lifting in the back-end, but will they be needed in the front, e.g. hotel reservations desk apps, could all be done by Browser, increasing security by limiting what the equipment can do.  You might already see part of this occurring with WebOS, where the services it provides is of importance, not really what it is resting on.
&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I think what he is talking about is that all the regular joe user needs is access to the net/cloud and everything is provisioned there.  Hence do we need Win / Linux / etc. to do that, maybe its enough to just get the network connection and browser up, forget the rest.  Of course there shall still be need for OS\&#8217;s to do the heavy lifting in the back-end, but will they be needed in the front, e.g. hotel reservations desk apps, could all be done by Browser, increasing security by limiting what the equipment can do.  You might already see part of this occurring with WebOS, where the services it provides is of importance, not really what it is resting on.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: marlonrod</title>
		<link>http://www.linux-mag.com/id/7532/#comment-7027</link>
		<dc:creator>marlonrod</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.linux-mag.com/id/7532/#comment-7027</guid>
		<description>&lt;p&gt;CPU and memory management, file management, some type of interface/API, network interface management, these are things that would be needed by your so called services to work in a \&quot;workload container\&quot;. Isn\&#039;t that the definition of an OS? http://www.britannica.com/EBchecked/topic/429897/operating-system   If what you mean is that they will be streamlined, slim OSes to host the service then sure, that\&#039;s what ESXi is.  Since ESXi does all the things mentioned at the beginning of my comment then it\&#039;s by definition an OS.&lt;/p&gt;
&lt;p&gt;If on the other hand you are talking about some type of \&quot;black box\&quot; service that basically runs on an specific hardware with its own OS that does only what that service needs it to do then sure I could see where that could try to become a trend but it all depends on the same things as OS and virtual machines combos: budget, resources, manageability, etc.
&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>CPU and memory management, file management, some type of interface/API, network interface management, these are things that would be needed by your so called services to work in a \&#8221;workload container\&#8221;. Isn\&#8217;t that the definition of an OS? <a href="http://www.britannica.com/EBchecked/topic/429897/operating-system" rel="nofollow">http://www.britannica.com/EBchecked/topic/429897/operating-system</a>   If what you mean is that they will be streamlined, slim OSes to host the service then sure, that\&#8217;s what ESXi is.  Since ESXi does all the things mentioned at the beginning of my comment then it\&#8217;s by definition an OS.</p>
<p>If on the other hand you are talking about some type of \&#8221;black box\&#8221; service that basically runs on an specific hardware with its own OS that does only what that service needs it to do then sure I could see where that could try to become a trend but it all depends on the same things as OS and virtual machines combos: budget, resources, manageability, etc.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mkozikowski</title>
		<link>http://www.linux-mag.com/id/7532/#comment-7028</link>
		<dc:creator>mkozikowski</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.linux-mag.com/id/7532/#comment-7028</guid>
		<description>&lt;p&gt;I think that the basis of an OS is to provide a layer between the hardware and the program. Remember the days of VESA drivers?&lt;/p&gt;
&lt;p&gt;If we establish a VM with a fixed interface then one can start programming to the VM (hardware layer) directly. This gets us passed the need for a \&quot;Traditional\&quot; OS.&lt;/p&gt;
&lt;p&gt;There is are problems here, though. Who is in control of the VM? Not all VMs are equal. And we don\&#039;t want to become slaves to Software providers. And certainly the developer is not going to have a VM for every piece of hardware that is developed.&lt;/p&gt;
&lt;p&gt;Many Linux users create special tools to perform their work. Many times these tools can be used by others. And then they can be expanded to become the next \&quot;great\&quot; thing.&lt;/p&gt;
&lt;p&gt;So, I can see here a need for an OS workload.
&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I think that the basis of an OS is to provide a layer between the hardware and the program. Remember the days of VESA drivers?</p>
<p>If we establish a VM with a fixed interface then one can start programming to the VM (hardware layer) directly. This gets us passed the need for a \&#8221;Traditional\&#8221; OS.</p>
<p>There is are problems here, though. Who is in control of the VM? Not all VMs are equal. And we don\&#8217;t want to become slaves to Software providers. And certainly the developer is not going to have a VM for every piece of hardware that is developed.</p>
<p>Many Linux users create special tools to perform their work. Many times these tools can be used by others. And then they can be expanded to become the next \&#8221;great\&#8221; thing.</p>
<p>So, I can see here a need for an OS workload.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: fretter</title>
		<link>http://www.linux-mag.com/id/7532/#comment-7029</link>
		<dc:creator>fretter</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.linux-mag.com/id/7532/#comment-7029</guid>
		<description>&lt;p&gt;One (just one) of the reason virtualising is that it allows us to run many apps simultaneously on a single piece of hardware without the hassle of trying to get them all to work side by side in one OS instance; i.e. circumventing the fagility of contemporary OS and app combinations.  &lt;/p&gt;
&lt;p&gt;This means we have 2 layers of OS, the hypervisor and the guest, which can only degrade the native performance available to app.&lt;/p&gt;
&lt;p&gt;However, if we (the IT community, open and closed source) were to properly get our act together we would create a robust mainstream OS that will handle app co-existance without running into dependancy problems and unexpected resource contention issues.&lt;/p&gt;
&lt;p&gt;Surely we DO NOT want to be forever hamstrung by the performance and feature limitations of the instruction masking of any VM platform.  Surely we DO want to be able to take advantage of new hardware as soon as it is released, without having to wait for a hypervisor upgrade, or be beholden to a company that slows to a crawl in a financial crisis?&lt;/p&gt;
&lt;p&gt;Paul Fretter
&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>One (just one) of the reason virtualising is that it allows us to run many apps simultaneously on a single piece of hardware without the hassle of trying to get them all to work side by side in one OS instance; i.e. circumventing the fagility of contemporary OS and app combinations.  </p>
<p>This means we have 2 layers of OS, the hypervisor and the guest, which can only degrade the native performance available to app.</p>
<p>However, if we (the IT community, open and closed source) were to properly get our act together we would create a robust mainstream OS that will handle app co-existance without running into dependancy problems and unexpected resource contention issues.</p>
<p>Surely we DO NOT want to be forever hamstrung by the performance and feature limitations of the instruction masking of any VM platform.  Surely we DO want to be able to take advantage of new hardware as soon as it is released, without having to wait for a hypervisor upgrade, or be beholden to a company that slows to a crawl in a financial crisis?</p>
<p>Paul Fretter</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jpurdy</title>
		<link>http://www.linux-mag.com/id/7532/#comment-7030</link>
		<dc:creator>jpurdy</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.linux-mag.com/id/7532/#comment-7030</guid>
		<description>&lt;p&gt;Death to windows via virtualization!!
&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Death to windows via virtualization!!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sbirkett</title>
		<link>http://www.linux-mag.com/id/7532/#comment-7031</link>
		<dc:creator>sbirkett</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.linux-mag.com/id/7532/#comment-7031</guid>
		<description>&lt;p&gt;let face it , unless an application can manage all the hardware resources of the hardware it runs on, you will need some kind of software service like an OS to take care of that work.
&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>let face it , unless an application can manage all the hardware resources of the hardware it runs on, you will need some kind of software service like an OS to take care of that work.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: thecatch</title>
		<link>http://www.linux-mag.com/id/7532/#comment-7032</link>
		<dc:creator>thecatch</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.linux-mag.com/id/7532/#comment-7032</guid>
		<description>&lt;p&gt;Scheduling these workloads and making them perform well, that is the job of the OS.&lt;/p&gt;
&lt;p&gt;Virtualization is the partitioning of the machine &amp; it\&#039;s resources, it\&#039;s not efficient computing. It\&#039;s really not needed to achieve the computing world discussed in this article. A simple utility application can provide partitioned data results, (output), without the need of virtulization or VM (virtual machines).&lt;/p&gt;
&lt;p&gt;This article is right on, especially the VUI discussion. WINDOWS was a GUI based OS, but a poor performing scheduling and multi-tasking OS.&lt;/p&gt;
&lt;p&gt;This article describes what the future could look like and will look like. But performance will play a factor, and Virtualization does not provide improved performance. In fact it slows down performance.&lt;/p&gt;
&lt;p&gt;A new platform (OS) is being developed by many, a parallel processing software based platform, that will provide performance gains. This OS will provide the performance and the underbelly power &amp; scheduling needs of an OS, and it will lead us forward.
&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Scheduling these workloads and making them perform well, that is the job of the OS.</p>
<p>Virtualization is the partitioning of the machine &#38; it\&#8217;s resources, it\&#8217;s not efficient computing. It\&#8217;s really not needed to achieve the computing world discussed in this article. A simple utility application can provide partitioned data results, (output), without the need of virtulization or VM (virtual machines).</p>
<p>This article is right on, especially the VUI discussion. WINDOWS was a GUI based OS, but a poor performing scheduling and multi-tasking OS.</p>
<p>This article describes what the future could look like and will look like. But performance will play a factor, and Virtualization does not provide improved performance. In fact it slows down performance.</p>
<p>A new platform (OS) is being developed by many, a parallel processing software based platform, that will provide performance gains. This OS will provide the performance and the underbelly power &#38; scheduling needs of an OS, and it will lead us forward.</p>
]]></content:encoded>
	</item>
</channel>
</rss>