Article:
  Panther Maintenance Tips
Subject:   Latest update and update:prebinding
Date:   2005-09-23 16:56:43
From:   Tigerlover
Before the latest combined security and iPod update (of 22nd sept. 05) I first make the repair permissions & disk from Tigers installationdisc. After that I restart from the HD on my PowerBook and does a "sudo update_prebinding -root / -force" in Terminal.


After this process I make both updates and installation hereof. Fine enough...


After that I once more runs the repair of af permissions & disk fra the installationsdisc, restarts again from PowerBooks harddisk og does a "sudo update_prebinding -root / -force" in Terminal - and expects that I then just have to restart to have completed the whole thing according to the book....


...but in Terminal something has been written I have not seen before:


update_prebinding: temp file missing: /usr/lib/libz.1.2.3_redoprebinding.dylib


It makes me a bit nerveous - 'cause what's this - and what does it mean???


Has it got something to do with the updates?


I try the whole process in Terminal three times - but this message is written in Terminal at the end of the update_prebinding every time...


?????

Full Threads Oldest First

Showing messages 1 through 1 of 1.

  • FJ de Kermadec photo Latest update and update:prebinding
    2005-09-24 11:52:45  FJ de Kermadec | O'Reilly Blogger [View]

    Hi!

    First of all, thank you very much for your message and for taking the time to post!

    Updating the prebinding is not an obligatory task and should only be performed when you notice an inexplicable performance lag. As a general rule, performing it before and/or after system updates will not have an effect on the installation of this update, especially as most Apple installers do this for you at the end of the process (the task you see called "Optimizing".)

    This being said, seeing error messages during an Update_Prebinding process should not, in itself, be cause for concern. Indeed, many files cannot be prebound for many reasons and your Mac is ready to handle that eventuality. The command is merely letting you know about what it encounters.

    Once again, thanks for posting!

    FJ