You've not done much Unix administration have you ? As a Unix systems administrator, I can tell you all the issues you've raised are barely non-issues.
You're not very good at gauging your audience are you? I doesn't matter what my level of Unix experience is, my post was meant for AVERAGE desktop users, not system administrators. Your post somehow magically assumes EVERYONE ON HERE has those skills. And even if they did, it's still going to be faster in OSX to simply reboot off the backup (i.e. 1-2 minutes maximum) than attempt to find the source of the problem AND correct it in less time. But even if it always took less time than a reboot, MOST users on here don't have those skills and thus your advice is worthless to the majority on here and hence my reply to contrast yours. While your reply may be correct for you and a few others, it's little more than arrogance and bad advice for what I would wager is the vast majority of the users on here who are not expert Unix or Linux administrators.
Once OSX has a problem at the core level, it cannot necessarily be fixed at the GUI level. You are then dealing with a Unix problem, not a "Mac" one so-to-speak and this is why I brought up Linux to compare. Most Mac users do not have that kind of knowledge and thus telling them to 'fix' it is not very good advice, IMO, especially when tools like CCC guarantee an instant working OS on a simple reboot in 1-2 minutes where you can then restore (and perhaps fix what went wrong the first time).
For example, one time a software update in Leopard completely screwed up OSX here (normal applications were crapping out instantly, etc. if I recall correctly). This was apparently a defect in that software update (the combo update apparently lacked the problem at that time). It was far simpler to boot off my backup drive, restore the original (so the backup wouldn't be in danger if I tried again) and then use the combo update instead at which point the original updated correctly and problem solved. Trying to repair something when I have no idea what the software update was even modifying would have been a NIGHTMARE.
Now I'm sure you, being a wunderkind, would have fired up the VI and fixed that baby in 10 seconds flat without even opening your eyes, but I think most people would have found it sounder advice to keep a CCC type bootable backup around and never have to worry about it.
I'll be happy to go into further detail about specific Linux things you brought up below, but first:
How about keeping a backup around of the download ? Then you can just run it in place over anything really, it's simply an application.
A backup of what? The guy asked about whether he'd need 10.6.8 before he could install Lion and the answer is YES, he'll need to update to it first before he can then update to Lion (thus doubling the install time for Lion). If he doesn't have 10.6.0 installed (i.e. still using Leopard), he'll need to install that FIRST and THEN update to 10.6.8 and THEN update to Lion, which can more than triple the time it would have taken if Apple provided a direct update (which could have been just a file sold at the Apple store online even) that could update from Leopard instead of an "App Store Only" Lion that needs App store functionality and thus 10.6.8 (apparently even 10.6.7 isn't enough even though it has basic App Store support).
Now that we've dealt with that seemingly random comment, let's get back to why Linux tends to suck for new users and why OSX is awesome if you backup your drive with CCC or equiv.
First, Linux installs like booting off of anything. File pointers ? Setup up your grub properly and there is basically 0 issues. Same with LILO or loadlin
Please explain that to the average new desktop Linux user when it simply dumps them into a Grub prompt and won't boot. They insert their rescue disc they created when they installed whatever version of Linux and it gets them to another (different) shell prompt where they are perhaps instructed to go ahead and fix whatever the problem is (no help). Yes, it's real user friendly...if you're a Linux nerd, that is.
😉
Hell, you can boot to safe and be denied the ability to even write to your own filesystem at first. Try tooling around Linux forums and chat areas to find answers for those sorts of things if you're in a hurry (and that assumes you can boot into Windows or have a 2nd computer, etc. to even get to the Net for help). You can read a book or two on Unix and still not know what to do in certain situations. Don't even get me started on often cryptic 'man' pages that look like they were written by someone who has English for a 3rd language.
🙄 Most hacker types oddly aren't into documentation.
I HAVE fixed problems that way before, but it's not always pleasant, IMO. You need to know exactly where the problem is and what you need to do to fix it or you have a fun day ahead of you. And let me tell you in the past all it took to screw up an X config file was one wrong character. Explain that to an average user who simply wants to add a second monitor or a mouse that won't auto-configure, etc. (more common in the past, but then some distros are very old fashioned). I've been there in the past. It's a good learning experience, of course, but no much fun if you just want to get some work outside the computer OS itself done.
These things happen less in more recent distrobutions, but once you think it would be cool to modify the setup to a more customized experience, you can quickly find yourself in situations like this. I remember setting up automatic joystick detection long before there was ever any GUI controls to set the scripts up, etc. Most Linux types back then saw no need for such things. They could cite 2-3 letter linux commands from memory in a second flat, but couldn't write a decent document page to save their lives. And the elitist attitudes were unbearable...say you're a Linux admin? That explains a LOT.
😉