<?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 5</title>
	<atom:link href="http://news.opensuse.org/2008/01/16/opensuse-weekly-news-issue-5/feed/" rel="self" type="application/rss+xml" />
	<link>http://news.opensuse.org/2008/01/16/opensuse-weekly-news-issue-5/</link>
	<description>The latest news from the openSUSE project</description>
	<lastBuildDate>Mon, 13 Feb 2012 22:54:51 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Dow</title>
		<link>http://news.opensuse.org/2008/01/16/opensuse-weekly-news-issue-5/comment-page-1/#comment-2350</link>
		<dc:creator>Dow</dc:creator>
		<pubDate>Tue, 22 Jan 2008 05:56:55 +0000</pubDate>
		<guid isPermaLink="false">http://news.opensuse.org/2008/01/16/opensuse-weekly-news-issue-5/#comment-2350</guid>
		<description>I agree some notice on news.opensuse.org or on the top page of the main portal, or even on the download page would have been a big reassurance.  Being down that long threw off automatic updates on all the community repositories on all the machines I manage.  Every single machine is a tuned mix of main and community repository based software.  Very few mirrors had all the software available from what I found.  I think the project has probably learned a lesson here in failover planning so I hope this never happens again.  However, this is where the rubber meets the road on business versus hobby support.  Do I really need to bite the bullet a pay for SLED&#039;s support, or can OpenSuSE fit my needs properly?  I&#039;ve used SuSE and OpenSuSE for many years in the business setting with great dependability, however, it is only in the past few years that the distro is recycled so quickly and is much more dependent on online repositories.  I&#039;d really like a five year security support plan for all OpenSuSE software, and rock solid dependability on the online repositories.  However, I think only SLED will ever have that policy.  But, I love the constant mix of updated software every six months to a year that you just don&#039;t get with SLED.  So, I&#039;ll stick with OpenSuSE and set up my own mirror for syncing.  I still haven&#039;t found any distro to compare with OpenSuSE for my needs.
Best wishes,
Dow</description>
		<content:encoded><![CDATA[<p>I agree some notice on news.opensuse.org or on the top page of the main portal, or even on the download page would have been a big reassurance.  Being down that long threw off automatic updates on all the community repositories on all the machines I manage.  Every single machine is a tuned mix of main and community repository based software.  Very few mirrors had all the software available from what I found.  I think the project has probably learned a lesson here in failover planning so I hope this never happens again.  However, this is where the rubber meets the road on business versus hobby support.  Do I really need to bite the bullet a pay for SLED&#8217;s support, or can OpenSuSE fit my needs properly?  I&#8217;ve used SuSE and OpenSuSE for many years in the business setting with great dependability, however, it is only in the past few years that the distro is recycled so quickly and is much more dependent on online repositories.  I&#8217;d really like a five year security support plan for all OpenSuSE software, and rock solid dependability on the online repositories.  However, I think only SLED will ever have that policy.  But, I love the constant mix of updated software every six months to a year that you just don&#8217;t get with SLED.  So, I&#8217;ll stick with OpenSuSE and set up my own mirror for syncing.  I still haven&#8217;t found any distro to compare with OpenSuSE for my needs.<br />
Best wishes,<br />
Dow</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ande J</title>
		<link>http://news.opensuse.org/2008/01/16/opensuse-weekly-news-issue-5/comment-page-1/#comment-2315</link>
		<dc:creator>Ande J</dc:creator>
		<pubDate>Sat, 19 Jan 2008 10:57:10 +0000</pubDate>
		<guid isPermaLink="false">http://news.opensuse.org/2008/01/16/opensuse-weekly-news-issue-5/#comment-2315</guid>
		<description>Hi, I did actually have to install during the time the servers were down. Why? Because my hardware broke... Ironic I guess but back to the issue, the installation worked fine without any of the online repositories so I don&#039;t get the point made above that this would not work. Ok the update step failed and I had to wait a couple of days to get my system back to the way I&#039;m used to having it but it was no major problem. And as I&#039;m not paying a penny on running a really good OS I can live with this. I have no idea how much effort it would be, but if I were to run an enterprise and its survival would rely on externally hosted update sites, I&#039;d make sure I&#039;d have my own mirror...

Best Regards,

Andre</description>
		<content:encoded><![CDATA[<p>Hi, I did actually have to install during the time the servers were down. Why? Because my hardware broke&#8230; Ironic I guess but back to the issue, the installation worked fine without any of the online repositories so I don&#8217;t get the point made above that this would not work. Ok the update step failed and I had to wait a couple of days to get my system back to the way I&#8217;m used to having it but it was no major problem. And as I&#8217;m not paying a penny on running a really good OS I can live with this. I have no idea how much effort it would be, but if I were to run an enterprise and its survival would rely on externally hosted update sites, I&#8217;d make sure I&#8217;d have my own mirror&#8230;</p>
<p>Best Regards,</p>
<p>Andre</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Doug Glenn</title>
		<link>http://news.opensuse.org/2008/01/16/opensuse-weekly-news-issue-5/comment-page-1/#comment-2291</link>
		<dc:creator>Doug Glenn</dc:creator>
		<pubDate>Fri, 18 Jan 2008 14:27:51 +0000</pubDate>
		<guid isPermaLink="false">http://news.opensuse.org/2008/01/16/opensuse-weekly-news-issue-5/#comment-2291</guid>
		<description>Being a cheerleader will not exonerate the issue of being down, and the lack of communication.  72 hours down in web space is an eternity for any online entity.  The issue is Novells support and communication, not the community.  Chill?  It didn&#039;t bother me personally.  From a technical and business standpoint it was a disaster, and any attempt to portray it as anything less is sad. There was also the poor disaster recovery planning and lack of failover.  Call it harsh, but when one of the premier FOSS sites goes offline and stays offline for days it is an issue and a black eye on those involved.  If you don&#039;t hold those reponsible for the failures feet to the fire, it could very well happen again. That would be more tragic. 

Put your self into the shoes of a total newbie and their frustration.  The loss of confidence in the system.  Movement elsewhere.  All of which could have been relieved by timely communication.  That is why simply saying &quot;there is a problem&quot; and leaving it at that is insufficient, both from a business and customer support standpoint.  This is an old type of geek arrogance that doesn&#039;t play well in the real world.  Go ahead and tell me to chill, go ahead and bash the messenger.  Then read about a good example of how it should have been handled:  http://blogs.zdnet.com/projectfailures/?p=567

Questions now?  The point here, is this is supposed to be a &quot;professional&quot; site. It should be run that way, and communication should be kept open, no matter how embarrassing it may seem initially.  If there had been some sort of notice saying, &quot;Equipment on order, we will be starting up some of the systems in X hours&quot;, followed up by &quot;X systems are now up, but the following still have issues, X time is still needed&quot;.  If this had occurred, then I would have said nothing.  But the silence was all we got after the initial announcement. And did any of you attempt an installation during this time period?  If you had, then you would have seen and experienced the problem a newbie would have encountered.  You can&#039;t do an install anymore WITHOUT the site being online successfully (no error messages).  This is another problem that should be addressed with the distro.

Do you honestly believe the upper muckity mucks at Novell are going to give a rats behind unless someone acts pissy about it?  I don&#039;t.  I&#039;ve dealt with Novell since 1992 and Suse since 1997.  Credit goes where credit is due, and so does the mud.  I buy the distribution myself, not simply download it.  How the hell else are they going to make money to keep going?  So I will bitch if I want to.  I&#039;ve paid for the right.  I am willing to bet those asking me to &#039;chill&#039; haven&#039;t.  Freeloaders don&#039;t have much right to complain. Ponder that as well.

BTW, the comment on 30,000 children starving is a total read herring or non-sequitor (sp?) and is only an attempt to draw attention off the actual issue.</description>
		<content:encoded><![CDATA[<p>Being a cheerleader will not exonerate the issue of being down, and the lack of communication.  72 hours down in web space is an eternity for any online entity.  The issue is Novells support and communication, not the community.  Chill?  It didn&#8217;t bother me personally.  From a technical and business standpoint it was a disaster, and any attempt to portray it as anything less is sad. There was also the poor disaster recovery planning and lack of failover.  Call it harsh, but when one of the premier FOSS sites goes offline and stays offline for days it is an issue and a black eye on those involved.  If you don&#8217;t hold those reponsible for the failures feet to the fire, it could very well happen again. That would be more tragic. </p>
<p>Put your self into the shoes of a total newbie and their frustration.  The loss of confidence in the system.  Movement elsewhere.  All of which could have been relieved by timely communication.  That is why simply saying &#8220;there is a problem&#8221; and leaving it at that is insufficient, both from a business and customer support standpoint.  This is an old type of geek arrogance that doesn&#8217;t play well in the real world.  Go ahead and tell me to chill, go ahead and bash the messenger.  Then read about a good example of how it should have been handled:  <a href="http://blogs.zdnet.com/projectfailures/?p=567" rel="nofollow">http://blogs.zdnet.com/projectfailures/?p=567</a></p>
<p>Questions now?  The point here, is this is supposed to be a &#8220;professional&#8221; site. It should be run that way, and communication should be kept open, no matter how embarrassing it may seem initially.  If there had been some sort of notice saying, &#8220;Equipment on order, we will be starting up some of the systems in X hours&#8221;, followed up by &#8220;X systems are now up, but the following still have issues, X time is still needed&#8221;.  If this had occurred, then I would have said nothing.  But the silence was all we got after the initial announcement. And did any of you attempt an installation during this time period?  If you had, then you would have seen and experienced the problem a newbie would have encountered.  You can&#8217;t do an install anymore WITHOUT the site being online successfully (no error messages).  This is another problem that should be addressed with the distro.</p>
<p>Do you honestly believe the upper muckity mucks at Novell are going to give a rats behind unless someone acts pissy about it?  I don&#8217;t.  I&#8217;ve dealt with Novell since 1992 and Suse since 1997.  Credit goes where credit is due, and so does the mud.  I buy the distribution myself, not simply download it.  How the hell else are they going to make money to keep going?  So I will bitch if I want to.  I&#8217;ve paid for the right.  I am willing to bet those asking me to &#8216;chill&#8217; haven&#8217;t.  Freeloaders don&#8217;t have much right to complain. Ponder that as well.</p>
<p>BTW, the comment on 30,000 children starving is a total read herring or non-sequitor (sp?) and is only an attempt to draw attention off the actual issue.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard</title>
		<link>http://news.opensuse.org/2008/01/16/opensuse-weekly-news-issue-5/comment-page-1/#comment-2289</link>
		<dc:creator>Richard</dc:creator>
		<pubDate>Thu, 17 Jan 2008 23:18:47 +0000</pubDate>
		<guid isPermaLink="false">http://news.opensuse.org/2008/01/16/opensuse-weekly-news-issue-5/#comment-2289</guid>
		<description>Who cares if it went down for 72 hours, really.  30,000 children are dieing each day from starvation around the world.  And you get your knickers in a twist over problems that couldn&#039;t be helped that took it down for 72 hours.  Oh my.  Imagine all the things you could of done for 72 hours.  Instead of sitting their wetting yourself.  Novell and Opensuse let no body down.  Because most people are intelligent to know that these things happen with technology, and will always happen.  Doug, no one needs to come clean, for god sake, you aren&#039;t paying them for their service, they are giving it to you free, get off your high horse and apologize for being a twat</description>
		<content:encoded><![CDATA[<p>Who cares if it went down for 72 hours, really.  30,000 children are dieing each day from starvation around the world.  And you get your knickers in a twist over problems that couldn&#8217;t be helped that took it down for 72 hours.  Oh my.  Imagine all the things you could of done for 72 hours.  Instead of sitting their wetting yourself.  Novell and Opensuse let no body down.  Because most people are intelligent to know that these things happen with technology, and will always happen.  Doug, no one needs to come clean, for god sake, you aren&#8217;t paying them for their service, they are giving it to you free, get off your high horse and apologize for being a twat</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Beineri</title>
		<link>http://news.opensuse.org/2008/01/16/opensuse-weekly-news-issue-5/comment-page-1/#comment-2286</link>
		<dc:creator>Beineri</dc:creator>
		<pubDate>Thu, 17 Jan 2008 20:56:57 +0000</pubDate>
		<guid isPermaLink="false">http://news.opensuse.org/2008/01/16/opensuse-weekly-news-issue-5/#comment-2286</guid>
		<description>No, Friday.</description>
		<content:encoded><![CDATA[<p>No, Friday.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://news.opensuse.org/2008/01/16/opensuse-weekly-news-issue-5/comment-page-1/#comment-2285</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Thu, 17 Jan 2008 19:25:38 +0000</pubDate>
		<guid isPermaLink="false">http://news.opensuse.org/2008/01/16/opensuse-weekly-news-issue-5/#comment-2285</guid>
		<description>It´s 20:30 hours and still nothing :-{</description>
		<content:encoded><![CDATA[<p>It´s 20:30 hours and still nothing :-{</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: AlbertoP</title>
		<link>http://news.opensuse.org/2008/01/16/opensuse-weekly-news-issue-5/comment-page-1/#comment-2283</link>
		<dc:creator>AlbertoP</dc:creator>
		<pubDate>Thu, 17 Jan 2008 17:16:35 +0000</pubDate>
		<guid isPermaLink="false">http://news.opensuse.org/2008/01/16/opensuse-weekly-news-issue-5/#comment-2283</guid>
		<description>Today :-)</description>
		<content:encoded><![CDATA[<p>Today :-)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Xniver</title>
		<link>http://news.opensuse.org/2008/01/16/opensuse-weekly-news-issue-5/comment-page-1/#comment-2281</link>
		<dc:creator>Xniver</dc:creator>
		<pubDate>Thu, 17 Jan 2008 16:07:37 +0000</pubDate>
		<guid isPermaLink="false">http://news.opensuse.org/2008/01/16/opensuse-weekly-news-issue-5/#comment-2281</guid>
		<description>When alpha 1 will be out?</description>
		<content:encoded><![CDATA[<p>When alpha 1 will be out?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SneWs</title>
		<link>http://news.opensuse.org/2008/01/16/opensuse-weekly-news-issue-5/comment-page-1/#comment-2280</link>
		<dc:creator>SneWs</dc:creator>
		<pubDate>Thu, 17 Jan 2008 15:35:44 +0000</pubDate>
		<guid isPermaLink="false">http://news.opensuse.org/2008/01/16/opensuse-weekly-news-issue-5/#comment-2280</guid>
		<description>What? Get out more, come on people. It&#039;s cold out here, much better off in here infront of the computer writing my own wonderful world ;)</description>
		<content:encoded><![CDATA[<p>What? Get out more, come on people. It&#8217;s cold out here, much better off in here infront of the computer writing my own wonderful world ;)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: anothersatisfiedcustomer</title>
		<link>http://news.opensuse.org/2008/01/16/opensuse-weekly-news-issue-5/comment-page-1/#comment-2279</link>
		<dc:creator>anothersatisfiedcustomer</dc:creator>
		<pubDate>Thu, 17 Jan 2008 13:30:41 +0000</pubDate>
		<guid isPermaLink="false">http://news.opensuse.org/2008/01/16/opensuse-weekly-news-issue-5/#comment-2279</guid>
		<description>seriously, some people need to get out more. There are mirror servers dotted throughout the world hosting the ftp server contents. If you need to download something so desperately that you cannot wait, use one of these. I happen to use the UK mirror hosted by www.mirrorservice.org in preference to the main opensuse ones because they are far quicker for me to download from living in UK.</description>
		<content:encoded><![CDATA[<p>seriously, some people need to get out more. There are mirror servers dotted throughout the world hosting the ftp server contents. If you need to download something so desperately that you cannot wait, use one of these. I happen to use the UK mirror hosted by <a href="http://www.mirrorservice.org" rel="nofollow">http://www.mirrorservice.org</a> in preference to the main opensuse ones because they are far quicker for me to download from living in UK.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

