It always matters when you update software, period. Always wait a while before updating anything on the computer, especially if you're in the middle of an extensive project. Anything can happen. If you have a compulsion to update things the second they come out, then you must be prepared to endure the consequences.If iTunes isn't a part of your workflow, it shouldn't matter if you update iTunes.
It's the whole application, just as it always is.Glad they fixed it so fast, but Jesus, 233 mb's to do it?
It's the whole application, just as it always is.
Wonder why they can't simply patch instead of replacing the whole app every time.
Glad they fixed it so fast, but Jesus, 233 mb's to do it?
Nothing? I was working on a project at 2 am while I discovered I could not copy my 70gb project folder over to my laptop via thunderbolt because the users folder was hidden. I needed to get up at 5:30 am to bring the project over to a finishing suite to meet the clients deadline. This bug was not "absolutely nothing".
I wonder if around Steve this could ever happen...
I think the drop down menus are much easier to understand than what I envision a radio button UI would look and respond.
Are you saying that the hiding of the Users folder suddenly made the File Sharing not operable between computers? And the "Go to Folder..." command in Finder suddenly stopped working for you?
In this day and age, you're doing manual copying of project files rather than using a file syncing technology such as Dropbox?
Yes... this bug was a minor inconvenience, but definitely not as show-stopping as you portray it to be. You were hit with it due to your chosen workflow and your lack of knowledge about basic Finder and Terminal commands. You should be thankful for this bug, because it has given you a chance to learn something that you otherwise wouldn't have learned.![]()
It always matters when you update software, period. Always wait a while before updating anything on the computer, especially if you're in the middle of an extensive project. Anything can happen. If you have a compulsion to update things the second they come out, then you must be prepared to endure the consequences.
I'd still give it a week to see if any new nasties come to light, although if there were any problems with the stock iApps / Office / Adobe CS I think we'd have heard by now.So is it safe to update now? It's times like these that make me wary of installing updates as soon as they come out. I usually wait a week before I update.
When Steve was alive, Apple shipped a version of iTunes that wiped your disk if your disk was named wrong. Mistakes happen.
I hope you aren't a sys admin for a living.
Heartbleed bug? I better wait a week to see if anyone he any problems before updating just in case!
It's never Apples fault, is it?
----------
Its 2014 and Apple still hasn't figured out patching vs downloading an entire new build.
I remember the story, although I don't think I knew *anyone* who was actually using (or attempting to use) OS X 10.1 at the time...I dont recall this, maybe it was before 2007 or somehow this missed my OSX
Apple said:This is to notify you that Apple has identified an installer issue with iTunes 2.0 for Mac OS X that affects a limited number of systems running Mac OS X with multiple volumes (drives or partitions) mounted. For those systems, running the iTunes 2.0 installer can result in loss of user data. While this error is highly unlikely to affect most users, Apple strongly advises that anyone who has downloaded the 2.0 version of iTunes for Mac OS X, as well as anyone who has a beta version of iTunes 2.0 for Mac OS X, immediately remove the iTunes.pkg installer file from their system. A new version that corrects this issue, iTunes 2.0.1 for Mac OS X, is now available for downloading at www.apple.com/itunes. Users who have already installed iTunes 2.0 without incident do not need to reinstall iTunes 2.0.1, but they should still immediately remove the 2.0 installer file from their system. This issue does not affect users of iTunes 2.0 for Mac OS 9.
Wonder why they can't simply patch instead of replacing the whole app every time.
Software updates already have a whole host of variables, adding patching to the mix compounds the issue by orders of magnitude.
Both network bandwidth and disk space are no longer at the premium they were even 5 years ago.
I'd rather Apple remove as many variables as possible, and "waste" disk and network resources.
11.2.1 is not an entire new build. It's also a patch.
If iTunes isn't a part of your workflow, it shouldn't matter if you update iTunes.
Do I really need to point out who's fault it is that you applied a system update and an update to a *media player* to a critical production machine approaching a deadline?
Yes. Apple shouldn't have broken it. But your problem was entirely of your own making.
People need to actually realize what they're doing.
----------
Not so, as the hidden attribute and the permissions change was getting re-applied after a restart.
----------
The system doesn't re-run postinstall scripts on every restart.