<?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: Hi BIOS! My Name Is &#8220;Linux&#8221;, Or Is It?</title>
	<atom:link href="http://tech.shantanugoel.com/2008/08/03/hi-bios-my-name-is-linux-or-is-it.html/feed" rel="self" type="application/rss+xml" />
	<link>http://tech.shantanugoel.com/2008/08/03/hi-bios-my-name-is-linux-or-is-it.html</link>
	<description>Shantanu's Gadgets, Gizmos, Hacks, Tips, Tricks, Technology...and your kitchen sink</description>
	<lastBuildDate>Sat, 13 Mar 2010 08:29:49 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: DimWit</title>
		<link>http://tech.shantanugoel.com/2008/08/03/hi-bios-my-name-is-linux-or-is-it.html#comment-4870</link>
		<dc:creator>DimWit</dc:creator>
		<pubDate>Fri, 24 Oct 2008 11:37:54 +0000</pubDate>
		<guid isPermaLink="false">http://tech.shantanugoel.com/2008/08/03/hi-bios-my-name-is-linux-or-is-it.html#comment-4870</guid>
		<description>Can someone tell me why the BIOS should care what OS is going to run? I thought it would be up to the OS to deal with whatever data the BIOS throws at it -  as long as it standard driven.</description>
		<content:encoded><![CDATA[<p>Can someone tell me why the BIOS should care what OS is going to run? I thought it would be up to the OS to deal with whatever data the BIOS throws at it &#8211;  as long as it standard driven.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike</title>
		<link>http://tech.shantanugoel.com/2008/08/03/hi-bios-my-name-is-linux-or-is-it.html#comment-4866</link>
		<dc:creator>Mike</dc:creator>
		<pubDate>Fri, 24 Oct 2008 11:22:54 +0000</pubDate>
		<guid isPermaLink="false">http://tech.shantanugoel.com/2008/08/03/hi-bios-my-name-is-linux-or-is-it.html#comment-4866</guid>
		<description>Ill give a link that explains the reasoning imo 
http://www.custompc.co.uk/news/604521/foxconn-sabotages-bios-to-stop-linux-running.html</description>
		<content:encoded><![CDATA[<p>Ill give a link that explains the reasoning imo<br />
<a href="http://www.custompc.co.uk/news/604521/foxconn-sabotages-bios-to-stop-linux-running.html" rel="nofollow">http://www.custompc.co.uk/news/604521/foxconn-sabotages-bios-to-stop-linux-running.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ken Jennings</title>
		<link>http://tech.shantanugoel.com/2008/08/03/hi-bios-my-name-is-linux-or-is-it.html#comment-4865</link>
		<dc:creator>Ken Jennings</dc:creator>
		<pubDate>Fri, 24 Oct 2008 11:15:09 +0000</pubDate>
		<guid isPermaLink="false">http://tech.shantanugoel.com/2008/08/03/hi-bios-my-name-is-linux-or-is-it.html#comment-4865</guid>
		<description>DRM was my first thought too.  I&#039;d suspect motherboard/bios makers of being in cahoots with Microsoft and using this &quot;feature&quot; to disable or reduce hardware functionality if a Microsoft-approve OS is not running the system.</description>
		<content:encoded><![CDATA[<p>DRM was my first thought too.  I&#8217;d suspect motherboard/bios makers of being in cahoots with Microsoft and using this &#8220;feature&#8221; to disable or reduce hardware functionality if a Microsoft-approve OS is not running the system.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Louis</title>
		<link>http://tech.shantanugoel.com/2008/08/03/hi-bios-my-name-is-linux-or-is-it.html#comment-4836</link>
		<dc:creator>Louis</dc:creator>
		<pubDate>Thu, 23 Oct 2008 20:02:34 +0000</pubDate>
		<guid isPermaLink="false">http://tech.shantanugoel.com/2008/08/03/hi-bios-my-name-is-linux-or-is-it.html#comment-4836</guid>
		<description>Does anyone think that this is to disable functionality if the OS is not one that adheres to DRM standards.</description>
		<content:encoded><![CDATA[<p>Does anyone think that this is to disable functionality if the OS is not one that adheres to DRM standards.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nathan</title>
		<link>http://tech.shantanugoel.com/2008/08/03/hi-bios-my-name-is-linux-or-is-it.html#comment-4835</link>
		<dc:creator>Nathan</dc:creator>
		<pubDate>Thu, 23 Oct 2008 20:01:05 +0000</pubDate>
		<guid isPermaLink="false">http://tech.shantanugoel.com/2008/08/03/hi-bios-my-name-is-linux-or-is-it.html#comment-4835</guid>
		<description>The difference between Linux and Windows in this area is that if there is a problem with a motherboard/bios feature and Linux then Linux is likely to have a work around within a short amount of time.  BIOS is firmware and should probably be replaced less often than an OS kernel, so this makes sense, but with Windows there aren&#039;t the same fixes and the board producers are trying to work out of the box with versions of Windows rather than allowing all features.
Too bad BIOS and OS don&#039;t negotiate on features; something similar to the LCP layer of PPP.</description>
		<content:encoded><![CDATA[<p>The difference between Linux and Windows in this area is that if there is a problem with a motherboard/bios feature and Linux then Linux is likely to have a work around within a short amount of time.  BIOS is firmware and should probably be replaced less often than an OS kernel, so this makes sense, but with Windows there aren&#8217;t the same fixes and the board producers are trying to work out of the box with versions of Windows rather than allowing all features.<br />
Too bad BIOS and OS don&#8217;t negotiate on features; something similar to the LCP layer of PPP.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shantanu Goel</title>
		<link>http://tech.shantanugoel.com/2008/08/03/hi-bios-my-name-is-linux-or-is-it.html#comment-2138</link>
		<dc:creator>Shantanu Goel</dc:creator>
		<pubDate>Tue, 05 Aug 2008 17:38:59 +0000</pubDate>
		<guid isPermaLink="false">http://tech.shantanugoel.com/2008/08/03/hi-bios-my-name-is-linux-or-is-it.html#comment-2138</guid>
		<description>maccam, you are correct. But its so disgusting of bill to say that &quot;we do this work...and result is that linux works great without having to do the work&quot;. I mean, till now because of the crappy windows design linux has been doing ALL the work, and on top of that he talks of making it specially biased towards windows. I wonder what became of that case...</description>
		<content:encoded><![CDATA[<p>maccam, you are correct. But its so disgusting of bill to say that &#8220;we do this work&#8230;and result is that linux works great without having to do the work&#8221;. I mean, till now because of the crappy windows design linux has been doing ALL the work, and on top of that he talks of making it specially biased towards windows. I wonder what became of that case&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: maccam94</title>
		<link>http://tech.shantanugoel.com/2008/08/03/hi-bios-my-name-is-linux-or-is-it.html#comment-2112</link>
		<dc:creator>maccam94</dc:creator>
		<pubDate>Mon, 04 Aug 2008 21:39:18 +0000</pubDate>
		<guid isPermaLink="false">http://tech.shantanugoel.com/2008/08/03/hi-bios-my-name-is-linux-or-is-it.html#comment-2112</guid>
		<description>My only guess is that Windows does not support &quot;capability checks&quot; like that. Nor would they want to implement it when:
A) __OSI works fine for them
B) It helps Linux
&quot;Bill Gates muses on the merits of making ACPI extentions &quot;somehow Windows specific.&quot;, continuing to say &quot;If (sic) seems unfortunate if we do this work and get our partners to do the work and the result is that Linux works great without having to do the work.&quot; In the same memo, he suggest defining &quot;the APIs so that they work well with NT and not the others, even if they are open.&quot;&quot;
http://antitrust.slated.org/www.iowaconsumercase.org/011607/3000/PX03020.pdf

So basically it would be up to the BIOS manufacturers to do this specially for Linux.</description>
		<content:encoded><![CDATA[<p>My only guess is that Windows does not support &#8220;capability checks&#8221; like that. Nor would they want to implement it when:<br />
A) __OSI works fine for them<br />
B) It helps Linux<br />
&#8220;Bill Gates muses on the merits of making ACPI extentions &#8220;somehow Windows specific.&#8221;, continuing to say &#8220;If (sic) seems unfortunate if we do this work and get our partners to do the work and the result is that Linux works great without having to do the work.&#8221; In the same memo, he suggest defining &#8220;the APIs so that they work well with NT and not the others, even if they are open.&#8221;"<br />
<a href="http://antitrust.slated.org/www.iowaconsumercase.org/011607/3000/PX03020.pdf" rel="nofollow">http://antitrust.slated.org/www.iowaconsumercase.org/011607/3000/PX03020.pdf</a></p>
<p>So basically it would be up to the BIOS manufacturers to do this specially for Linux.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
