Posted: 5/30/2012 8:58:49 AM EDT
|
|
Windows 7 boots very quickly.
OSX also boot quickly. use whichever one you like. I use both. quoted because this is my experience as well. Quoted:
My Windows 7 machines boot up very quickly (I buy and/or build quality). <–– Typed on a MacBook Pro, running OSX Lion, that booted very quickly this morning. |
|
Quoted: Quoted: It's not funny b/c it's not true.... Correct. There's usually no reason to restart a Mac. There was a planned power outage at my workplace over the weekend. I had to cold-start OSX. It took an amazingly long time. (Yes, I did shut the machine down gracefully before the outage.) My 5-year-old Windows 2003 server at home typically goes for several months without any need for a restart. |
|
Quoted:
Windows 7 boots very quickly. OSX also boot quickly. use whichever one you like. I use both. quoted because this is my experience as well. Quoted:
My Windows 7 machines boot up very quickly (I buy and/or build quality). <–– Typed on a MacBook Pro, running OSX Lion, that booted very quickly this morning. These. My windows 7 machine is built by me...boots just as fast as my MBP (partioned with OSX/Win7/Ubuntu). |
|
Quoted: Quoted: It's not funny b/c it's not true.... Correct. There's usually no reason to restart a Mac. Until a dumbass uses it.  That's 2 days of a dumbass.  My laptop boots to login in about 10 seconds, then to working dtop in another 10. It is usually ready before I am setup.
|
|
Quoted:
Quoted:
Quoted:
It's not funny b/c it's not true.... Correct. There's usually no reason to restart a Mac. Until a dumbass uses it. That's 2 days of a dumbass.
My laptop boots to login in about 10 seconds, then to working dtop in another 10. It is usually ready before I am setup. I still don't get why you keep posting that screenshot. All it's doing is a chgrp from 0 (wheel) to 80 (admin), both of which have exactly one member, root (no effective change). Then, it's doing a chmod from 664 to 644 (taking write permission from group 80, which is meaningless, since root is the only member anyway). Nothing is "broken", and the "fix" didn't do anything substantive. I could have sworn we've gone over this. 
|
|
Quoted: Quoted: Quoted: Quoted: It's not funny b/c it's not true.... Correct. There's usually no reason to restart a Mac. Until a dumbass uses it. That's 2 days of a dumbass. My laptop boots to login in about 10 seconds, then to working dtop in another 10. It is usually ready before I am setup. I still don't get why you keep posting that screenshot. All it's doing is a chgrp from 0 (wheel) to 80 (admin), both of which have exactly one member, root (no effective change). Then, it's doing a chmod from 664 to 644 (taking write permission from group 80, which is meaningless, since root is the only member anyway). Nothing is "broken", and the "fix" didn't do anything substantive. I could have sworn we've gone over this. I "Repair Permission" after big OS updates out of habit (someone once told me to do it many years ago). It's probably unnecessary, and the computer works totally fine before and after. I get a similar list of gibberish, which initially concerned me, until I found out it was inconsequential. Makes me wonder what the "dumb ass's" problem really was.... Oh well... the screenshot LOOKS impressive. |
|
Quoted: Quoted: Quoted: Quoted: Quoted: It's not funny b/c it's not true.... Correct. There's usually no reason to restart a Mac. Until a dumbass uses it. That's 2 days of a dumbass. My laptop boots to login in about 10 seconds, then to working dtop in another 10. It is usually ready before I am setup. I still don't get why you keep posting that screenshot. All it's doing is a chgrp from 0 (wheel) to 80 (admin), both of which have exactly one member, root (no effective change). Then, it's doing a chmod from 664 to 644 (taking write permission from group 80, which is meaningless, since root is the only member anyway). Nothing is "broken", and the "fix" didn't do anything substantive. I could have sworn we've gone over this. I "Repair Permission" after big OS updates out of habit (someone once told me to do it many years ago). It's probably unnecessary, and the computer works totally fine before and after. I get a similar list of gibberish, which initially concerned me, until I found out it was inconsequential. Makes me wonder what the "dumb ass's" problem really was.... Oh well... the pic LOOKS impressive. The computer was fully unable to boot in any way from the HDD and hardware was solid after testing. I would consider that a pretty substantive issue. Two days on limited permissions and he managed this. Permissions fix corrected this. Most OSX issues seem to come down to screwed up permissions like most windows issues are infection issues. |