<?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: Mac OS X 10.4.10: Damage in Pages and BBEdit</title>
	<atom:link href="http://www.betalogue.com/2007/07/02/mac-os-x-10410-damage-in-pages-and-bbedit/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.betalogue.com/2007/07/02/mac-os-x-10410-damage-in-pages-and-bbedit/</link>
	<description>Notes from an unfinished world…</description>
	<lastBuildDate>Mon, 06 Feb 2012 13:29:08 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Pierre Igot</title>
		<link>http://www.betalogue.com/2007/07/02/mac-os-x-10410-damage-in-pages-and-bbedit/comment-page-1/#comment-7185</link>
		<dc:creator>Pierre Igot</dc:creator>
		<pubDate>Tue, 03 Jul 2007 12:34:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.betalogue.com/2007/07/02/mac-os-x-10410-damage-in-pages-and-bbedit/#comment-7185</guid>
		<description>I am a SuperDuper! user too, although I do not use it to back up my entire startup volume. I only backup the user folders on the startup volume, and then all my documents, which are on another partition. I can see the idea of having a daily backup of your entire startup volume, but you still need to manually keep track of what you&#039;ve done between the time of the last backup and the time you realize that your updated system has a problem. So it&#039;s not a perfect solution either. 

Of course, an &quot;Archive and Install&quot; system replacement also has the disadvantage of breaking SD!&#039;s automatic backup schedule. So that&#039;s a bit of a pain.

Andrew: It&#039;s true that I probably should have tried to see if Pages and BBEdit were still working properly from within another user account. I&#039;ll try to remember the next time something like this happens… which of course I hope will not be for another few years!</description>
		<content:encoded><![CDATA[<p>I am a SuperDuper! user too, although I do not use it to back up my entire startup volume. I only backup the user folders on the startup volume, and then all my documents, which are on another partition. I can see the idea of having a daily backup of your entire startup volume, but you still need to manually keep track of what you&#8217;ve done between the time of the last backup and the time you realize that your updated system has a problem. So it&#8217;s not a perfect solution either. </p>
<p>Of course, an &#8220;Archive and Install&#8221; system replacement also has the disadvantage of breaking SD!&#8217;s automatic backup schedule. So that&#8217;s a bit of a pain.</p>
<p>Andrew: It&#8217;s true that I probably should have tried to see if Pages and BBEdit were still working properly from within another user account. I&#8217;ll try to remember the next time something like this happens… which of course I hope will not be for another few years!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew Aitken</title>
		<link>http://www.betalogue.com/2007/07/02/mac-os-x-10410-damage-in-pages-and-bbedit/comment-page-1/#comment-7184</link>
		<dc:creator>Andrew Aitken</dc:creator>
		<pubDate>Tue, 03 Jul 2007 09:48:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.betalogue.com/2007/07/02/mac-os-x-10410-damage-in-pages-and-bbedit/#comment-7184</guid>
		<description>Sounds pretty bad - I hate it when things go wrong like that, especially after you&#039;d just been bragging about the stability!

I left Apple a few months ago, so I&#039;m not on the front lines with any latest fixes for 10.4.10, and those log lines don&#039;t give much detail about the cause of the problem - but I can offer some advice, just like everyone else!

I always found it best to try things in a different user account before going onto an archive and install. You&#039;d be surprised how a seemingly unrelated preference or cache file could cause problems. I&#039;ve seen terminal preferences affect Adobe applications, and all sorts of other weird things... If it works in a new user, you&#039;ve narrowed it down to something in your home folder (bar a few items in /Library/Caches) - If it still doesn&#039;t work, then it&#039;s almost certainly system related and archive and install is probably going to be quicker and more reliable than narrowing down the precise cause of the fault.

Oh, historically I&#039;ve always used the combo updates even for point upgrades, just to cover my back with customers. I&#039;ve started just using software update myself now.</description>
		<content:encoded><![CDATA[<p>Sounds pretty bad &#8211; I hate it when things go wrong like that, especially after you&#8217;d just been bragging about the stability!</p>
<p>I left Apple a few months ago, so I&#8217;m not on the front lines with any latest fixes for 10.4.10, and those log lines don&#8217;t give much detail about the cause of the problem &#8211; but I can offer some advice, just like everyone else!</p>
<p>I always found it best to try things in a different user account before going onto an archive and install. You&#8217;d be surprised how a seemingly unrelated preference or cache file could cause problems. I&#8217;ve seen terminal preferences affect Adobe applications, and all sorts of other weird things&#8230; If it works in a new user, you&#8217;ve narrowed it down to something in your home folder (bar a few items in /Library/Caches) &#8211; If it still doesn&#8217;t work, then it&#8217;s almost certainly system related and archive and install is probably going to be quicker and more reliable than narrowing down the precise cause of the fault.</p>
<p>Oh, historically I&#8217;ve always used the combo updates even for point upgrades, just to cover my back with customers. I&#8217;ve started just using software update myself now.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: swissfondue</title>
		<link>http://www.betalogue.com/2007/07/02/mac-os-x-10410-damage-in-pages-and-bbedit/comment-page-1/#comment-7183</link>
		<dc:creator>swissfondue</dc:creator>
		<pubDate>Tue, 03 Jul 2007 08:50:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.betalogue.com/2007/07/02/mac-os-x-10410-damage-in-pages-and-bbedit/#comment-7183</guid>
		<description>My solution isi to create a bootable mirror backup of my HD onto an external drive with Superduper!
Then, all I need to do is copy this back to the HD. This way I keep all my preference settings, apps, serial numbers etc. and save a lot of time in case of update related issues.</description>
		<content:encoded><![CDATA[<p>My solution isi to create a bootable mirror backup of my HD onto an external drive with Superduper!<br />
Then, all I need to do is copy this back to the HD. This way I keep all my preference settings, apps, serial numbers etc. and save a lot of time in case of update related issues.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel A. Shockley</title>
		<link>http://www.betalogue.com/2007/07/02/mac-os-x-10410-damage-in-pages-and-bbedit/comment-page-1/#comment-7182</link>
		<dc:creator>Daniel A. Shockley</dc:creator>
		<pubDate>Tue, 03 Jul 2007 04:21:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.betalogue.com/2007/07/02/mac-os-x-10410-damage-in-pages-and-bbedit/#comment-7182</guid>
		<description>I run automated backups every night using SuperDuper, cloning the entire disk to an external drive. SD only updates what has changed, so it is quick, and it happens at 3:30 AM. 

I then apply System Updates and check things out, knowing that if something seems wrong, I can just do a copy the other way by booting off the external drive, as long as I do that before the next backup runs, and first grabbing my updated email folder (or any other new data files). This is also reassuring for potential data loss from drive failures, damage, theft, etc. 

External drives are cheap, and so is SuperDuper (or whatever you choose to use). An automated backup routine is worth at least 10 times what it costs in lost energy, anxiety, and especially lost information. I highly recommend it to everyone.</description>
		<content:encoded><![CDATA[<p>I run automated backups every night using SuperDuper, cloning the entire disk to an external drive. SD only updates what has changed, so it is quick, and it happens at 3:30 AM. </p>
<p>I then apply System Updates and check things out, knowing that if something seems wrong, I can just do a copy the other way by booting off the external drive, as long as I do that before the next backup runs, and first grabbing my updated email folder (or any other new data files). This is also reassuring for potential data loss from drive failures, damage, theft, etc. </p>
<p>External drives are cheap, and so is SuperDuper (or whatever you choose to use). An automated backup routine is worth at least 10 times what it costs in lost energy, anxiety, and especially lost information. I highly recommend it to everyone.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pierre Igot</title>
		<link>http://www.betalogue.com/2007/07/02/mac-os-x-10410-damage-in-pages-and-bbedit/comment-page-1/#comment-7181</link>
		<dc:creator>Pierre Igot</dc:creator>
		<pubDate>Tue, 03 Jul 2007 01:53:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.betalogue.com/2007/07/02/mac-os-x-10410-damage-in-pages-and-bbedit/#comment-7181</guid>
		<description>won: I forgot to mention that I did try re-applying the combo update a second time. It didn&#039;t help.

Thanks for the additional information and tips.</description>
		<content:encoded><![CDATA[<p>won: I forgot to mention that I did try re-applying the combo update a second time. It didn&#8217;t help.</p>
<p>Thanks for the additional information and tips.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: won</title>
		<link>http://www.betalogue.com/2007/07/02/mac-os-x-10410-damage-in-pages-and-bbedit/comment-page-1/#comment-7180</link>
		<dc:creator>won</dc:creator>
		<pubDate>Mon, 02 Jul 2007 21:49:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.betalogue.com/2007/07/02/mac-os-x-10410-damage-in-pages-and-bbedit/#comment-7180</guid>
		<description>You can also try reinstalling the combo updater a second time.  

&lt;a href=&quot;http://applejack.sourceforge.net/&quot; rel=&quot;nofollow&quot;&gt;AppleJack&lt;/a&gt; can also be useful when weirdness strikes.  For a deep cleanse that eliminates built-up grime, type &lt;code&gt;applejack AUTO restart&lt;/code&gt; at single user startup (Command-s at reboot) after it&#039;s installed.   

Anything that avoids the effort of a full reinstall is worth it for me (uh...anything free, that is :-).</description>
		<content:encoded><![CDATA[<p>You can also try reinstalling the combo updater a second time.  </p>
<p><a href="http://applejack.sourceforge.net/" rel="nofollow">AppleJack</a> can also be useful when weirdness strikes.  For a deep cleanse that eliminates built-up grime, type <code>applejack AUTO restart</code> at single user startup (Command-s at reboot) after it&#8217;s installed.   </p>
<p>Anything that avoids the effort of a full reinstall is worth it for me (uh&#8230;anything free, that is :-).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: spectralhuman</title>
		<link>http://www.betalogue.com/2007/07/02/mac-os-x-10410-damage-in-pages-and-bbedit/comment-page-1/#comment-7179</link>
		<dc:creator>spectralhuman</dc:creator>
		<pubDate>Mon, 02 Jul 2007 21:33:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.betalogue.com/2007/07/02/mac-os-x-10410-damage-in-pages-and-bbedit/#comment-7179</guid>
		<description>as an independant tech support guy, I update hundreds of macs...  I have never had a problem installing an update.  I have worked out this procedure over several years and it hasn&#039;t failed me yet.

step 1. reboot

step 2. repair permissions

step 3. run maintenance scripts using MainMenu (http://www.macupdate.com/info.php/id/17111)

step 4. clean user cache using MainMenu

step 5. Run diskwarrior

step 6. Install update using combo updater.

There are some other apps you can use to run maint. scripts and clean caches... onyx, cocktail, etc...

I think the most important things to do are first reboot, repair permissions and run maint. scripts...

Mac OS X is incredibly stable, but computers are &quot;inherently unstable systems&quot;™ and need to be rebooted at the very least before updates...</description>
		<content:encoded><![CDATA[<p>as an independant tech support guy, I update hundreds of macs&#8230;  I have never had a problem installing an update.  I have worked out this procedure over several years and it hasn&#8217;t failed me yet.</p>
<p>step 1. reboot</p>
<p>step 2. repair permissions</p>
<p>step 3. run maintenance scripts using MainMenu (<a href="http://www.macupdate.com/info.php/id/17111" rel="nofollow">http://www.macupdate.com/info.php/id/17111</a>)</p>
<p>step 4. clean user cache using MainMenu</p>
<p>step 5. Run diskwarrior</p>
<p>step 6. Install update using combo updater.</p>
<p>There are some other apps you can use to run maint. scripts and clean caches&#8230; onyx, cocktail, etc&#8230;</p>
<p>I think the most important things to do are first reboot, repair permissions and run maint. scripts&#8230;</p>
<p>Mac OS X is incredibly stable, but computers are &#8220;inherently unstable systems&#8221;™ and need to be rebooted at the very least before updates&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pierre Igot</title>
		<link>http://www.betalogue.com/2007/07/02/mac-os-x-10410-damage-in-pages-and-bbedit/comment-page-1/#comment-7178</link>
		<dc:creator>Pierre Igot</dc:creator>
		<pubDate>Mon, 02 Jul 2007 20:40:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.betalogue.com/2007/07/02/mac-os-x-10410-damage-in-pages-and-bbedit/#comment-7178</guid>
		<description>I have always used combo updaters, so I am not sure why all of a sudden it would have become a problem. Unfortunately, due to bandwidth limitations, I tend to download stand-alone updaters in a location other than my home office, especially when they are very large, so I always end up using a less-travelled route anyway. I also need to keep a local copy of the updater (for myself and for other people), so it makes much more sense to have the combo updater that will work with any version of 10.4.</description>
		<content:encoded><![CDATA[<p>I have always used combo updaters, so I am not sure why all of a sudden it would have become a problem. Unfortunately, due to bandwidth limitations, I tend to download stand-alone updaters in a location other than my home office, especially when they are very large, so I always end up using a less-travelled route anyway. I also need to keep a local copy of the updater (for myself and for other people), so it makes much more sense to have the combo updater that will work with any version of 10.4.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: AlanY</title>
		<link>http://www.betalogue.com/2007/07/02/mac-os-x-10410-damage-in-pages-and-bbedit/comment-page-1/#comment-7177</link>
		<dc:creator>AlanY</dc:creator>
		<pubDate>Mon, 02 Jul 2007 19:34:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.betalogue.com/2007/07/02/mac-os-x-10410-damage-in-pages-and-bbedit/#comment-7177</guid>
		<description>Wow, that sounds like a terrible experience.

I would strongly suggest not applying the combined update when you don&#039;t need to.  Even though it seems to make intuitive sense, the safer route with software is usually to go with the most well-travelled path, because that&#039;s the path that has been most heavily tested.  The majority of people will be using the regular updater, and so that will have the heaviest coverage from a testing perspective.  It probably won&#039;t make any difference for files that are part of the updates, but for configuration/plist file updates, I can see a lot of complexity that gets introduced in the combined updater that isn&#039;t present in the regular updater.  That&#039;s probably what went wrong for you.

Fortunately, I haven&#039;t had problems with 10.4.10, except for the odd little quirk that Apple Remote Desktop seems to list servers running 10.4.10 as running 10.4.9.</description>
		<content:encoded><![CDATA[<p>Wow, that sounds like a terrible experience.</p>
<p>I would strongly suggest not applying the combined update when you don&#8217;t need to.  Even though it seems to make intuitive sense, the safer route with software is usually to go with the most well-travelled path, because that&#8217;s the path that has been most heavily tested.  The majority of people will be using the regular updater, and so that will have the heaviest coverage from a testing perspective.  It probably won&#8217;t make any difference for files that are part of the updates, but for configuration/plist file updates, I can see a lot of complexity that gets introduced in the combined updater that isn&#8217;t present in the regular updater.  That&#8217;s probably what went wrong for you.</p>
<p>Fortunately, I haven&#8217;t had problems with 10.4.10, except for the odd little quirk that Apple Remote Desktop seems to list servers running 10.4.10 as running 10.4.9.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

