Apple releases Mac OS X 10.4.8 Update

24567

Comments

  • Reply 21 of 123
    Man, it's about time!!! Although, I was very surprised to see it released out in the morning hours though. Normally, they wait until in the afternoon hours. My guess is that they didn't want to waste anymore time on getting it released out!!!
     0Likes 0Dislikes 0Informatives
  • Reply 22 of 123
    Quote:
    Originally Posted by crees!


    Wrong-o Batman. Where the heck is that article when I need it? Errr.



    I would like to read that article. Before you speak your blasphemy, you should back it up. I have never ever had a problem arise from repairing permissions. I have done it thousands and thousands of times. If it is good to do when something is going wrong, then how could it be bad if those problems just haven't shown them themselves yet? I am sorry, I just can't go along with your heresy.
     0Likes 0Dislikes 0Informatives
  • Reply 23 of 123
    kickahakickaha Posts: 8,760member
    kim kap, you're an evil, evil man.
     0Likes 0Dislikes 0Informatives
  • Reply 24 of 123
    louzerlouzer Posts: 1,054member
    Quote:
    Originally Posted by Chucker


    Repair permissions when something's weird.

    Don't repair permissions just because.



    End of debate.



    Since repairing permissions can do no harm, and takes all of 30 seconds to a minute, its a step that, if someone wants to do, let them do it. The "You should never" vs. the "Always do" debate is really pointless.



    Now, something like the "You should rebuild your desktop monthly" debates of OS 8 days, or the "Defragging your computer will speed things up immensely!" arguments, those make more sense (as the time it takes to perform the tasks are greater, and certainly can cause as many problems as they cure).



    And if you want a "End of debate" item, it would be something like:



    "Never, ever, install anything made by Symantec.

    End of debate"
     0Likes 0Dislikes 0Informatives
  • Reply 25 of 123
    Quote:
    Originally Posted by rain


    Installed the update (combo).

    After it rebooted, HDD went nuts, and still is... a process 'mdimport' is crunching away like crazy.

    Photoshop works fine.

    When the HDD stops working, i'll repair permissions (which I was told you should always do, by the guru's here), and then restart and watch my baby sing.



    mdimport = spotlight



    repairing permissions = retarded
     0Likes 0Dislikes 0Informatives
  • Reply 27 of 123
    Quote:
    Originally Posted by techno


    If it is good to do when something is going wrong, then how could it be bad if those problems just haven't shown them themselves yet?



    Except that it's not even something good to do when something goes wrong. I don't think there's any evidence anywhere that it has ever solved a single problem.



    I don't think there's any harm in it, but if you're going to just waste time on something useless, try something fun at least. Like chanting and swinging a dead possum over your head.
     0Likes 0Dislikes 0Informatives
  • Reply 28 of 123
    Jesus christ.. stop arguing about repair permissions.... You don't have to do anything... especially if there are no problems... If there is a permissions issue preventing you from booting.. you can always boot to your Tiger CD and run Disk Utility and repair the permissions! Apple has never said to repair permissions after an update, and only mention it as a possible step in troubleshooting a problem.



    Most issues that arise with updates, have nothing to do with permissions.
     0Likes 0Dislikes 0Informatives
  • Reply 29 of 123
    what does repair premissions mean
     0Likes 0Dislikes 0Informatives
  • Reply 30 of 123
    You should always repair permissions before AND after repairing permissions.
     0Likes 0Dislikes 0Informatives
  • Reply 31 of 123
    Quote:
    Originally Posted by chris v


    You should always repair permissions before AND after repairing permissions.



    You forgot during.
     0Likes 0Dislikes 0Informatives
  • Reply 32 of 123
    pt123pt123 Posts: 696member
    Why does Apple not take an official position on repairing permissions instead of a bunch of folks on a forum?
     0Likes 0Dislikes 0Informatives
  • Reply 33 of 123
    I've just repaired permissions on this thread. Please let me know if this has caused any issues.
     0Likes 0Dislikes 0Informatives
  • Reply 34 of 123
    Something interesting taking place with my Macbook... I've never noticed the Apple logo on the back laptop display being illuminated upon closing. Almost all the time the display kills the backlight the moment that I close the lid... it took at least an extra second to second and a half to shut off..
     0Likes 0Dislikes 0Informatives
  • Reply 35 of 123
    outsideroutsider Posts: 6,008member
    Quote:
    Originally Posted by chris v


    You should always repair permissions before AND after repairing permissions.



    I laughed out loud when I read this. Thanks.



    BTW, i can't remember the last time I repaired permissions on my computer.
     0Likes 0Dislikes 0Informatives
  • Reply 36 of 123
    outsideroutsider Posts: 6,008member
    Quote:
    Originally Posted by Matthew Yohe


    Something interesting taking place with my Macbook... I've never noticed the Apple logo on the back laptop display being illuminated upon closing. Almost all the time the display kills the backlight the moment that I close the lid... it took at least an extra second to second and a half to shut off..



    That's a 'feature'.
     0Likes 0Dislikes 0Informatives
  • Reply 37 of 123
    mr. hmr. h Posts: 4,870member
    Quote:
    Originally Posted by kim kap sol


    You should never, EVER, repair permissions. I've heard stories of people getting their HDs wiped and their gym locker combination erased because they repaired permission. Trust me.







    Sol, look what you've done to the thread! Brilliant! I wouldn't have thought that repair permissions could have made me laugh so much.



    For those that haven't been around so long:



    About every-other-time there's an OS X update, the AppleInsider thread devoted to said update becomes a massive long debate about whether you should repair permissions before running an update or not. In versions of OS X prior to 10.4, repairing permissions took a very long time, so pointlessly repairing permissions before every update wasted a significant amount of time in total.



    However, now 10.4 doesn't take so long to do it, I can't see the harm. I don't bother myself, but I'd say the probability of it helping or making no difference is higher that the probability of it causing a problem.
     0Likes 0Dislikes 0Informatives
  • Reply 38 of 123
    maccrazymaccrazy Posts: 2,658member
    Quote:
    Originally Posted by kim kap sol


    You should never, EVER, repair permissions. I've heard stories of people getting their HDs wiped and their gym locker combination erased because they repaired permission. Trust me.







    kim kap sol you're an absolute legend!
     0Likes 0Dislikes 0Informatives
  • Reply 39 of 123
    mr. memr. me Posts: 3,221member
    Quote:
    Originally Posted by rafa


    what does repair premissions mean



    Repairing permissions does not actually repair anything. It resets permissions to their values stored in each file's respective receipts bundle. This is useful when misbehaving installers change permissions without restoring them when they finish. Repairing permissions cannot help you lose weight, win the big game, hit the lottery, or get the head cheerleader to give you the time of day. In the vast majority of cases, it is probably a waste of time, but it cannot do anything to damage your system. .
     0Likes 0Dislikes 0Informatives
  • Reply 40 of 123




    22 mandatory steps to upgrade OS X:



    00) Repair permissions.

    01) Purchase plane ticket to India, train ticket to Tibet, plane ticket to Benin.

    03) Repair permissions.

    04) Go to India, take bus to the foot of K2. Do not go to Mt. Everest, the DOS/BIOS guru lives there, that line is VERY long.

    05) Repair permissions.

    06a) Hire about two dozen sherpas (as you've never done any form of real exercise), climb to top of K2 or,

    06b) Rent RV, take Interstate 666 to top of K2.

    07) Repair permissions.

    08) Ask OX X guru for the true number of the beast, it will give you a list of randomly ordered steps (it is also of random length) to upgrade OS X. Thus the need to make this holy journey in the first place, as no two lists from the OS X guru will ever be identical.

    09) Repair permissions.

    10) Go to K2 train station, take train to Tibet, visit Dali Lama, His Holiness will give you the truer number of the beast (a 1024-bit random number in binary format, convert to base 10 integer, this number is equal to the number of times you will need to repeat the OS X guru's list of steps (see Step 08 above)).

    11) Repair permissions.

    12) Take plane to Benin, visit Nana Buluku, she will tell you to "Go to jail, go directly to jail, do not pass go, do not collect 103,622 Benin francs." Jail in Beninese means home. If you don't hear her say these words your Mac is DOOMED!

    13) Repair permissions.

    14) Once home, fly Pope in from Rome, have him perform exorcism on your Mac, ask him for truest number of the beast (another 1024-bit binary number, this is the power to which you take the number given to you from the Dali Lama (see Step 10), fly Pope back to Rome.

    15) Repair permissions.

    16) Update OS X per Step 08 per Step 14 times, remember to REPAIR PERMISSIONS after each iteration.

    17) Repair permissions (yes, you MUST do it again even though you just did it after the last iteration in Step 16 above).

    18) Don't ever backup your system, no need to do a backup, as this is a foolproof method, it has never failed.

    19) Format HD, install OS X from your CD's/DVD's, install update, install applications, recreate all lost data from scratch.

    20) Repair permissions.

    21) Repair permissions (while standing on your head).





     0Likes 0Dislikes 0Informatives
Sign In or Register to comment.