<?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: openSUSE Weekly News, Issue 114 is out!</title>
	<atom:link href="http://news.opensuse.org/2010/03/13/opensuse-weekly-news-issue-114-is-out/feed/" rel="self" type="application/rss+xml" />
	<link>http://news.opensuse.org/2010/03/13/opensuse-weekly-news-issue-114-is-out/</link>
	<description>The latest news from the openSUSE project</description>
	<lastBuildDate>Sat, 18 May 2013 19:45:57 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: CS</title>
		<link>http://news.opensuse.org/2010/03/13/opensuse-weekly-news-issue-114-is-out/comment-page-1/#comment-8424</link>
		<dc:creator>CS</dc:creator>
		<pubDate>Mon, 15 Mar 2010 19:08:10 +0000</pubDate>
		<guid isPermaLink="false">http://news.opensuse.org/?p=3017#comment-8424</guid>
		<description><![CDATA[If anyone is able to set-up a SAMBA Server to work with a common workgroup NO DC,then Domain,then Domain DC.. using only the GUI tools in Yast, System Settings and Dolphin somewhere in that great. It does not work! How we end up with our own written GUI which still fails today is beyond me.

How we end up with a Display that declares Read Only, when in fact a directory is RW, and God help anyone using Yast to create a NEW shared Directory via the GUI because if your create a new newly directory it belongs to root.Just hw you going to share that one
The &#039;defaults&#039; button on all displays does not function, You cannot change, edit, modify, edit the default in ANY SAMBA printer via GUI.

If the developers will actually use the desktop they release in their day to day work environment, bugs would not even get to beta. This also means NO command prompt usage, you have all the GUI tools a user has...See if you can function, using only the desktop functions and tools we give the market as release. Its clear NO developer ever uses our product on a day to day]]></description>
		<content:encoded><![CDATA[<p>If anyone is able to set-up a SAMBA Server to work with a common workgroup NO DC,then Domain,then Domain DC.. using only the GUI tools in Yast, System Settings and Dolphin somewhere in that great. It does not work! How we end up with our own written GUI which still fails today is beyond me.</p>
<p>How we end up with a Display that declares Read Only, when in fact a directory is RW, and God help anyone using Yast to create a NEW shared Directory via the GUI because if your create a new newly directory it belongs to root.Just hw you going to share that one<br />
The &#8216;defaults&#8217; button on all displays does not function, You cannot change, edit, modify, edit the default in ANY SAMBA printer via GUI.</p>
<p>If the developers will actually use the desktop they release in their day to day work environment, bugs would not even get to beta. This also means NO command prompt usage, you have all the GUI tools a user has&#8230;See if you can function, using only the desktop functions and tools we give the market as release. Its clear NO developer ever uses our product on a day to day</p>
]]></content:encoded>
	</item>
</channel>
</rss>
