<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.3" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: org.freedesktop.Hal.Device.SystemPowerManagement and the user</title>
	<link>http://blogs.gnome.org/hughsie/2007/10/13/orgfreedesktophaldevicesystempowermanagement-and-the-user/</link>
	<description>My fiancee is like Windows Vista: Looks pretty, difficult to understand and sometimes unpredictable...</description>
	<pubDate>Mon, 08 Sep 2008 02:58:42 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.3</generator>
		<item>
		<title>By: Anonymous</title>
		<link>http://blogs.gnome.org/hughsie/2007/10/13/orgfreedesktophaldevicesystempowermanagement-and-the-user/#comment-129</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Sat, 13 Oct 2007 14:47:09 +0000</pubDate>
		<guid>http://blogs.gnome.org/hughsie/2007/10/13/orgfreedesktophaldevicesystempowermanagement-and-the-user/#comment-129</guid>
		<description>These changes reduce the window for failure, which is good (might want to add logic that requires say 15 minutes of battery life available even when on AC).  But ideally we would have a system which was resilient to e.g. power loss in the middle of an update.  Stateless Linux&apos; two-partition model is one approach: http://fedoraproject.org/wiki/StatelessLinux Another would be to improve the various backends to be more journal-like.  Which gets to the point that hopefully packagekit will reduce the duplication among backends (since all they really are now is way overcomplicated ways to download glorified tarballs over HTTP and run shell scripts with make-style dependencies).</description>
		<content:encoded><![CDATA[<p>These changes reduce the window for failure, which is good (might want to add logic that requires say 15 minutes of battery life available even when on AC).  But ideally we would have a system which was resilient to e.g. power loss in the middle of an update.  Stateless Linux&apos; two-partition model is one approach: <a href="http://fedoraproject.org/wiki/StatelessLinux" rel="nofollow">http://fedoraproject.org/wiki/StatelessLinux</a> Another would be to improve the various backends to be more journal-like.  Which gets to the point that hopefully packagekit will reduce the duplication among backends (since all they really are now is way overcomplicated ways to download glorified tarballs over HTTP and run shell scripts with make-style dependencies).</p>
]]></content:encoded>
	</item>
</channel>
</rss>
