<?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: YaST module the C++ way</title>
	<atom:link href="http://lizards.opensuse.org/2008/07/15/yast-module-the-c-way/feed/" rel="self" type="application/rss+xml" />
	<link>http://lizards.opensuse.org/2008/07/15/yast-module-the-c-way/</link>
	<description>Blogs and Ramblings of the openSUSE Members</description>
	<lastBuildDate>Mon, 30 Jan 2012 19:11:21 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: J. Daniel Schmidt</title>
		<link>http://lizards.opensuse.org/2008/07/15/yast-module-the-c-way/#comment-178</link>
		<dc:creator>J. Daniel Schmidt</dc:creator>
		<pubDate>Mon, 18 Aug 2008 14:36:39 +0000</pubDate>
		<guid isPermaLink="false">http://lizards.opensuse.org/?p=99#comment-178</guid>
		<description>Just a note: This module is not meant to be a &quot;test all my hardware and its drivers and report any issues&quot; module  :)

The &quot;System and Hardware Information&quot; is no addition - it is already in the current registration module. But it never showed the data that would be sent. We just seprarated the workflow into 3 steps to make it more intuitive and in order to show the user, what actions will be performed.

The hardware data is basically the output of &quot;hwinfo&quot; - just go to your current registration module (aka. &quot;Online Update Configuration&quot;) and click on &quot;Details&quot; to see, what commands would be run if you wanted to send hardware data. There are no tests if a piece of hardware is failing or a driver is missing, we just collect the data that hwinfo outputs.
The data is used for statistics so we get an idea what hardware is important to support in future releases.</description>
		<content:encoded><![CDATA[<p>Just a note: This module is not meant to be a &#8220;test all my hardware and its drivers and report any issues&#8221; module  <img src='http://lizards.opensuse.org/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>The &#8220;System and Hardware Information&#8221; is no addition &#8211; it is already in the current registration module. But it never showed the data that would be sent. We just seprarated the workflow into 3 steps to make it more intuitive and in order to show the user, what actions will be performed.</p>
<p>The hardware data is basically the output of &#8220;hwinfo&#8221; &#8211; just go to your current registration module (aka. &#8220;Online Update Configuration&#8221;) and click on &#8220;Details&#8221; to see, what commands would be run if you wanted to send hardware data. There are no tests if a piece of hardware is failing or a driver is missing, we just collect the data that hwinfo outputs.<br />
The data is used for statistics so we get an idea what hardware is important to support in future releases.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ryan</title>
		<link>http://lizards.opensuse.org/2008/07/15/yast-module-the-c-way/#comment-176</link>
		<dc:creator>ryan</dc:creator>
		<pubDate>Sun, 10 Aug 2008 21:31:22 +0000</pubDate>
		<guid isPermaLink="false">http://lizards.opensuse.org/?p=99#comment-176</guid>
		<description>The &quot;System and Hardware Information&quot; is a nice addition on the testing side. Will it also report successful or failed hardware installations to SUSE, or provide the user with options if a piece of hardware fails to install?</description>
		<content:encoded><![CDATA[<p>The &#8220;System and Hardware Information&#8221; is a nice addition on the testing side. Will it also report successful or failed hardware installations to SUSE, or provide the user with options if a piece of hardware fails to install?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: HuHa</title>
		<link>http://lizards.opensuse.org/2008/07/15/yast-module-the-c-way/#comment-148</link>
		<dc:creator>HuHa</dc:creator>
		<pubDate>Thu, 17 Jul 2008 14:05:20 +0000</pubDate>
		<guid isPermaLink="false">http://lizards.opensuse.org/?p=99#comment-148</guid>
		<description>Huh? You can do that yourself. Just use /usr/bin/qtconfig .</description>
		<content:encoded><![CDATA[<p>Huh? You can do that yourself. Just use /usr/bin/qtconfig .</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: nobody</title>
		<link>http://lizards.opensuse.org/2008/07/15/yast-module-the-c-way/#comment-147</link>
		<dc:creator>nobody</dc:creator>
		<pubDate>Wed, 16 Jul 2008 05:34:51 +0000</pubDate>
		<guid isPermaLink="false">http://lizards.opensuse.org/?p=99#comment-147</guid>
		<description>Yea, it´s time to change color of YaST.It would be great.</description>
		<content:encoded><![CDATA[<p>Yea, it´s time to change color of YaST.It would be great.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

