<?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: Fatal mistakes in open-SUSE 11.1  Live CD</title>
	<atom:link href="http://www.marco.isrelated.com/?feed=rss2&#038;p=67" rel="self" type="application/rss+xml" />
	<link>http://www.marco.isrelated.com/?p=67</link>
	<description>Just another level of indirection.</description>
	<lastBuildDate>Wed, 06 Jan 2010 19:17:40 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Artem Miklich</title>
		<link>http://www.marco.isrelated.com/?p=67&#038;cpage=1#comment-128</link>
		<dc:creator>Artem Miklich</dc:creator>
		<pubDate>Mon, 26 Jan 2009 23:45:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.marco.isrelated.com/?p=67#comment-128</guid>
		<description>It has long been looking for this information, Thank you for your work.</description>
		<content:encoded><![CDATA[<p>It has long been looking for this information, Thank you for your work.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marco Antonio</title>
		<link>http://www.marco.isrelated.com/?p=67&#038;cpage=1#comment-125</link>
		<dc:creator>Marco Antonio</dc:creator>
		<pubDate>Tue, 13 Jan 2009 07:07:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.marco.isrelated.com/?p=67#comment-125</guid>
		<description>The machine dies about 12 hours (or more), after reading the processor and motherboard documentation, a possibility is that the RAM was corrupted too (one cannot adjust RAM slightly) since the wrong-update in the CMOS &quot;disturb&quot; other hardware or the ability of to identify it. So, only after a total discharge of the &quot;capacitors&quot; the machine was able to run again. These, are only suppositions -or superstitions-.
So, if the machine dies suddenly after running SUSE Live 11.1,  give it a chance in the &quot;styx&quot; maybe &quot;Charon&quot; can return the MB to you.</description>
		<content:encoded><![CDATA[<p>The machine dies about 12 hours (or more), after reading the processor and motherboard documentation, a possibility is that the RAM was corrupted too (one cannot adjust RAM slightly) since the wrong-update in the CMOS &#8220;disturb&#8221; other hardware or the ability of to identify it. So, only after a total discharge of the &#8220;capacitors&#8221; the machine was able to run again. These, are only suppositions -or superstitions-.<br />
So, if the machine dies suddenly after running SUSE Live 11.1,  give it a chance in the &#8220;styx&#8221; maybe &#8220;Charon&#8221; can return the MB to you.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: FuguRitual</title>
		<link>http://www.marco.isrelated.com/?p=67&#038;cpage=1#comment-124</link>
		<dc:creator>FuguRitual</dc:creator>
		<pubDate>Sun, 11 Jan 2009 07:23:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.marco.isrelated.com/?p=67#comment-124</guid>
		<description>Actually, the clock issue is a problem (LiveCD or Installed) for some ppl and making the change (set  &quot;SYSTOHC = no&quot;  in the  /etc/sysconfig/clock  file) that Marco provided does work.

However, Marco is incorrect about SUSE &quot;ruining the hardware&quot; or even about the &quot;CMOS info becoming shit.&quot;

For the few ppl affected, the time is changed in the other OS&#039;s on a multi-boot system because SUSE is changing the hardware clock.</description>
		<content:encoded><![CDATA[<p>Actually, the clock issue is a problem (LiveCD or Installed) for some ppl and making the change (set  &#8220;SYSTOHC = no&#8221;  in the  /etc/sysconfig/clock  file) that Marco provided does work.</p>
<p>However, Marco is incorrect about SUSE &#8220;ruining the hardware&#8221; or even about the &#8220;CMOS info becoming shit.&#8221;</p>
<p>For the few ppl affected, the time is changed in the other OS&#8217;s on a multi-boot system because SUSE is changing the hardware clock.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gabriel</title>
		<link>http://www.marco.isrelated.com/?p=67&#038;cpage=1#comment-123</link>
		<dc:creator>Gabriel</dc:creator>
		<pubDate>Sat, 10 Jan 2009 13:43:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.marco.isrelated.com/?p=67#comment-123</guid>
		<description>True. Asus MB, (p5xx-vm) 2 OSs, xp+suse11.1. I&#039;m at GMT +2. Suse modifies bios clock +2 hours every time I ran it.
Otherwise no harm done.
Thanks for the tip, I&#039;ve been searching for it.</description>
		<content:encoded><![CDATA[<p>True. Asus MB, (p5xx-vm) 2 OSs, xp+suse11.1. I&#8217;m at GMT +2. Suse modifies bios clock +2 hours every time I ran it.<br />
Otherwise no harm done.<br />
Thanks for the tip, I&#8217;ve been searching for it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marco Antonio</title>
		<link>http://www.marco.isrelated.com/?p=67&#038;cpage=1#comment-120</link>
		<dc:creator>Marco Antonio</dc:creator>
		<pubDate>Sun, 28 Dec 2008 06:47:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.marco.isrelated.com/?p=67#comment-120</guid>
		<description>The vista-theme is to perceive my disappointment with some linux distros, and since is a good wordpress-theme (I use the OS that works for each task) . Debian and the security packages, and now openSUSE modifies the hardware clock, without warning or some advice. 
Vista works fine on the same PC, unbelievable (since is a Microsoft product); a D865PERL Intel motherboard, P-IV HT 3Ghz, 4GB RAM, running a RHEL-5 clone, openBSD and Vista Ultimate.
[...] so, is not a matter of an OSs war[...] is a real issue on &quot;some hardware&quot; with this openSUSE live-CD, maybe the password protected BIOS?</description>
		<content:encoded><![CDATA[<p>The vista-theme is to perceive my disappointment with some linux distros, and since is a good wordpress-theme (I use the OS that works for each task) . Debian and the security packages, and now openSUSE modifies the hardware clock, without warning or some advice.<br />
Vista works fine on the same PC, unbelievable (since is a Microsoft product); a D865PERL Intel motherboard, P-IV HT 3Ghz, 4GB RAM, running a RHEL-5 clone, openBSD and Vista Ultimate.<br />
[...] so, is not a matter of an OSs war[...] is a real issue on &#8220;some hardware&#8221; with this openSUSE live-CD, maybe the password protected BIOS?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
