Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Apple Releases Safari 3.1.1, Addresses PWN2OWN Vulnerability
- Thread starter bcomer
- Start date
- Sort by reaction score
So........ back on topic.
Some of the 3.1.1 installation is done during system boot (you know, during the extra long gear churning right after POST). I'm curious how many people had their "gears" turning for an extra long time, like more than 30 seconds. All my Macs were done with this process in 30 seconds or less. Anyone have this problem? Any ideas why some systems had this problem and some didn't?
Some of the 3.1.1 installation is done during system boot (you know, during the extra long gear churning right after POST). I'm curious how many people had their "gears" turning for an extra long time, like more than 30 seconds. All my Macs were done with this process in 30 seconds or less. Anyone have this problem? Any ideas why some systems had this problem and some didn't?
On Windoze, running XP, it took longer to boot it up than usual (I had to do a reboot as well)
Haven't heard that one yet. Very interesting. I have no clue how an update on your Mac partition would affect your XP partition.
yeah, i suppose. but why would anyone say it's negative? just to do it to be dorks about it? it just urks me that no matter what the article is about, someone votes it negative. like enough of a percentage to notice it on a daily basis. like, the article could say "apple gives away free mac pros to everyone on mac rumors", and someone would vote it negative i guarantee.
just bugs me i guess.....
That is true.
With UNIX file-system semantics, a file's disk blocks are freed when the last directory entry is removed and the last open file handle referencing it is closed.
If you delete and replace a shared library, applications currently running will keep using the one they have. They'll use the new one when they quit and restart.
You could still get (from the OS) the list of applications that are using the library. The installer could then present you with the list and ask if you want to just terminate them or just reboot.
Even key system apps (like the Finder or the system UI server) can be restarted, although you might have to log out to make that happen.
I'm not on a Mac yet, I am running Safari for XP, and I was told to restart, and it took me longer than normal.
Oh, well that is interesting. On a Mac, part of the install is done during the restart. Maybe the same occurs for Windows. This would cause the delay.
You guys make it hard for someone to read this thread and determine whether they should install the update or not. hehe
It's not a big deal, but most people with Unix see a reboot as a cop-out. In other words, there's nothing that can be done in a reboot that couldn't be done at runtime.
In practice, it's easier for most end users to just do a reboot, but power users are forced to wonder.
Also, lately my laptop never works when I reboot to finish an installation. I have to reboot, then turn it off, turn it back on, and then it finishes correctly.
... aside from a kernel upgrade. But that's obviously not the situation here.
Most people (including me) are not having problems, but with every update, there are some people that to experience problems. This isn't unusual - the same thing happens with all software products from all manufacturers.
Sometimes the problem is self-inflicted, sometimes it's due to an incompatibility with some kind of haxie (which sometimes was installed surreptitiously - like the broken input managers that Logitech's keyboard and mouse software uses) sometimes the installation itself messes up, and sometimes there are other problems.
Always keep in mind that a web forum such as this one will give you a skewed perspective. People without problems don't post very many messages, while people with serious problems will post a lot. This should not be surprising to anyone, but you can definitely get an artificially-bad perspective if you forget this fact.
If you are truly worried, I recommend you
- Wait a week or two to update. If there is a serious problem that affects a lot of people (indicating an actual problem with the update and not some other factor that only affects a small number of users) then Apple will usually release another update within that time.
- Make a full backup before you update. If you experience a problem that you can't fix, you can restore your system from that backup to undo the update. You can do this yourself using your favorite backup system (including Time Machine) or you can use a program specially designed for this purpose (like Deep Freeze, which may be a good idea if you think may need to do this often.)
FWIW, I don't take any special measures. I make a full-system backup every week, as part of my routine system maintenance procedure. If an update truly messes up the system (which hasn't yet happened, thankfully), I can restore my system from the most recent backup.