Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Mac OS X gives you the choice to apply the update now or cancel it and apply it later, or not apply it at all. What's the problem? You have absolute control over what updates to apply and when.

The problem is that you can't tell it to update later. If you want to install it later, you need to actually remember there's an update waiting the next time you reboot and tell it to finally install the update. In Windows, when there's an update it installs it then gives you the option to reboot now or postpone it for a while (ranging from 5 minutes to 4 hours) then asks you again once the time period you selected ends. Once you're actually done working with your computer, the update is automatically applied, which is much more convenient.
 
I know. A couple of days ago I helped a friend that switched from Vista to a Mac set up some hard drives and install some software on his new Mac, and Snow Leopard was asking to deny/allow all the time. Every third mouse tap was to deny or allow and to enter the password. Suddenly he bursts out: ****, this is much worse than Vista! :rolleyes:

What are you doing to cause this? I've never seen this behavior in OS X.
 
Thats the dumbest thing I've ever herd, no offense. Do not try to defend windows reboot reputation by quoting the propaganda of some peice of softwares FAQ answer on why do I need to reboot after install. I can think of at least a dozen programs that are what a typical user would install, that have always, ALWAYS required a reboot of windows since the inception of the OS. Granted some of the reasons behind said reboots are as you listed, however I should not have to reboot my system for a software install. And by your definition that would also include, 90% of the updates that come around for the OS itself.

The only reason you are forced to reboot on the mac is like I said, because the average user doesn't know how to flush and reset the things necessary to do the update hot. If you did they would be optional for you as well.

I didn't want to get into this, but I don't think you know what you're talking about.

"Flushing" & "Resetting", as you put it, are simple operations that can be performed with a few extra lines of code in the installer performing the installation of an application (e.g. "InstallShield"). Mac OS X needs to reboot because the kernel (low-level core components) of the OS is being modified and the changes will only take effect after a complete recycle. The same holds true for Windows. This is basic OS science and architecture.

Sure, there was a time long ago when every Windows application under the sun required a reboot, but, as a former Windows application developer, I can tell you that this was more of a "best practice" in use by every Windows app developer, than it was a functional requirement. Haven't you ever tried to execute a Windows application (that asked you to reboot immediately after an initial install or upgrade), without rebooting, and it ran fine?

Can you name those dozen popular Windows applications in common usage today that require a reboot?
 
The problem is that you can't tell it to update later. ...
That's not true. You can either manually run Software Update at any time, or, if you're forgetful, you can have it check automatically:
Picture 1.jpg
 
That's not true. You can either manually run Software Update at any time, or, if you're forgetful, you can have it check automatically:
View attachment 212002
I don't think you're quite understanding correctly.

In Windows:

1) Windows Update will tell you there is an update available (or it will install it in the background automatically if you choose that option).

2) If that update needs a restart, the computer will ask if you want to restart immediately or wait until a more convenient time. Either way the update is installed, but not fully applied (because it needs to access system files that are in use). No matter which way you choose to restart (when Windows Update prompts you to, when you turn your computer off next etc.) the update will be installed then.

Ubuntu has similar functionality.

With Mac OS X, when an update is downloaded that needs a restart, you are asked if you want to install and restart now or cancel the update. There is no consistent prompting about that update once you decline to install it. For equivalent functionality to Windows, it would have to offer an option to install it the next time you reboot.
 
I don't think you're quite understanding correctly.

With Mac OS X, when an update is downloaded that needs a restart, you are asked if you want to install and restart now or cancel the update. There is no consistent prompting about that update once you decline to install it. For equivalent functionality to Windows, it would have to offer an option to install it the next time you reboot.

I understanding completely how Windows updates work, having been a Windows user since it was originally released. I don't want "equivalent functionality to Windows." If I did, I'd still be using Windows.

My point is, Mac OS X gives you the choice to install now, install later at a time of your choosing, or not at all. I don't want my system deciding if/when to install updates. I want to control that myself. I also don't want consistent annoying prompts when I elect to update later, and Mac OS X gives me that.
 
Mac OS X needs to reboot because the kernel (low-level core components) of the OS is being modified and the changes will only take effect after a complete recycle. The same holds true for Windows. This is basic OS science and architecture.

If these are indeed kernel patches, and you are/were a developer, than what is the opposition to reboots in this case? As for the couple added lines of code, I have seen plenty of non-kernel related updates roll thru that asked for a reboot. While you and I both know this could be avoided, doesn't mean it always is.

Sure, there was a time long ago when every Windows application under the sun required a reboot, but, as a former Windows application developer, I can tell you that this was more of a "best practice" in use by every Windows app developer, than it was a functional requirement. Haven't you ever tried to execute a Windows application (that asked you to reboot immediately after an initial install or upgrade), without rebooting, and it ran fine?

Never said it wouldn't run fine, merely that it requests the user to reboot. Just in kind there are a great many reboots requested of a user in OSX that don't actually require one. Which is exactly what I'm saying, in all honestly.

Can you name those dozen popular Windows applications in common usage today that require a reboot?

I'm sure I can't cause I dont spend my time installing windows software anymore. I use it windows as sparingly as life will allow. If indeed the practice of reboots after software installs is no longer the case, well good. ;)
 
With Mac OS X, when an update is downloaded that needs a restart, you are asked if you want to install and restart now or cancel the update.

That is certainly not my experience. I've often deferred a Restart without canceling the update. The update is then applied when I do Restart.
 
If that update needs a restart, the computer will ask if you want to restart immediately or wait until a more convenient time.
And it will keep bugging you about it until you finally restart (I think the longest you can say is "remind me in 4 hours") — often taking you out of a fullscreen app/game to tell you this.

It seems that every time I boot Windows (few times a week, probably) it has a new critical system update to install that requires a restart. At least in OS X I can tell it "not now" and I can just hide the SWU window and wait until I'm ready to restart.
 
  • Like
Reactions: jagooch
And it will keep bugging you about it until you finally restart (I think the longest you can say is "remind me in 4 hours") — often taking you out of a fullscreen app/game to tell you this.

It seems that every time I boot Windows (few times a week, probably) it has a new critical system update to install that requires a restart. At least in OS X I can tell it "not now" and I can just hide the SWU window and wait until I'm ready to restart.

Even worse is the default "Yes, reboot now" requires just either a space or an enter key press to automatically accept. The last company I was at had it so it would prompt you every 10 minutes, no way to change it. And if you were in the middle of typing something, since we were mostly code monkeys, we were always doing so. But the popup would take focus, being in the middle of typing, it isn't that uncommon to hit space or enter and have it quit your app and reboot right then and there! GRRRR!!!! Pain in the BUTT.
 
  • Like
Reactions: jagooch
He was updating the firmware af his external hard drives.

OS X should only prompt once to run content download from the Internet. If it were prompting within the app, then it's an issue with that particular app.
 
I agree, this has been getting worse and worse. If your installing new hardware, applications or rebuilding OSX I don't mind rebooting. But the occasional update seems to always need a reboot.

It's a hassle to me because of the programs I have running and the fact that because my G5 only has 3 USB ports I have to use hubs and after a reboot randomly some devices won't work unless they are unplugged and then plugged back in.

Maybe it's the fault of the devices that won't start, but it's still somewhat of a pain especially when someone else in the house thinks the computer is broken because the keyboard needs to be re-plugged in.:rolleyes:
 
And it will keep bugging you about it until you finally restart (I think the longest you can say is "remind me in 4 hours") — often taking you out of a fullscreen app/game to tell you this.

It seems that every time I boot Windows (few times a week, probably) it has a new critical system update to install that requires a restart. At least in OS X I can tell it "not now" and I can just hide the SWU window and wait until I'm ready to restart.

Windows updates only come out once a month, unless a very critical need arises. They come out on the second Tuesday of the month which is called "Black Tuesday" and the next day is called "Reboot Wednesday".

So if you were to catch up on all the updates, you shouldn't have to install/reboot more than once a month....there's no trickery there.
 
I've seen a bunch of gray screens of death in Tiger and Leopard.

What the hell is a grey screen of death, and come to think of it was does every computing glitch nowadays seems to have a "screen of death" appended to it. Perhaps people should try an give problems a descriptive name.
 
Bingo. But the fanboys conveniently ignore that fact. They also ignore the fact that Apple made a lot of fun of Vista's "Cancel or allow" feature, but that only a little time later Leopard was released with an also annoying "Deny/Allow" dialog.
...

The problem is if there is a system update with windows, you have to do it, otherwise you'll get constant nag screens or forced reboot, losing your unsaved work.

With OSX the user is in control, which a certain MS fanboy conveniently ignores.
 
The problem is if there is a system update with windows, you have to do it, otherwise you'll get constant nag screens or forced reboot, losing your unsaved work.

With OSX the user is in control, which a certain MS fanboy conveniently ignores.
I don't think you've been greeted by Software Update screens like I have. You're warned rather heavily about requiring a restart to update.

Otherwise Linux does have the advantage here for the most part.
 
Windows updates only come out once a month, unless a very critical need arises. They come out on the second Tuesday of the month which is called "Black Tuesday" and the next day is called "Reboot Wednesday".

So if you were to catch up on all the updates, you shouldn't have to install/reboot more than once a month....there's no trickery there.

Not 100% true, there are always updates of some type. Damn thing last week installed patches almost EVERYDAY! Then last night a huge one that took a good 1/2 hour to install. GAH! If it was truly once a month, it wouldn't be a problem, but damn, sometimes it is just too often. (this was on XP)
 
  • Like
Reactions: jagooch
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.