Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'already prebound?' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
already prebound?
Authored by: litedoctor on Apr 10, '01 11:31:12AM

Odd, I ran the prebinding command listed here, and all I got was a root prebound message an instant later. I thought it was supposed to take a while to run? Did I type it wrong (double checked, don't think so) or did my system get optimized all on its own?

B&W G3/300/192MB/6G, 9.1 and X on one partition.



[ Reply to This | # ]
already prebound?
Authored by: babbage on Apr 10, '01 04:54:22PM
I'm not sure. It's possible that your system was already updated. You can get information on the command by looking at it's help text or man[ual] page. (Sample output below, following the convention that the command prompt is denoted with a % and lines without the percent sign are generally the output of a command:
/Users/chris% which update_prebinding
/usr/bin/update_prebinding
/Users/chris% update_prebinding --help
Apr 10 16:31:48 update_prebinding[650] Start of update_prebinding
usage: prebind {-debug} {-verbose} {-root }
               (-pkgs ( )* ) | (-files file1 file2 ...)
  Calls redo_prebinding on executables and libraries in dependency order
  -verbose: display additional status and warning messages
  -debug: don't actually try to redo the prebinding for any files
  -pkgs: specifies package/install root pairs of changed files that require
         prebinding to be redone.
  -root: specifies the directory to be searched for dependent libraries
         If neither -pkgs or -file is specified, all libraries and executables in -root
         are rebound.
/Users/chris% man update_prebinding
[Omitted, see pages for yourself if you'd like. 
 Interestingly, the timestamp is 14 Feb 2001 --
 this seems to be something Apple is contributing
 to the BSD community.]

So, the command lives in /usr/bin with a lot of the other Unixy system stuff.

It looks like you could try to run it again with a -verbose flag to see if that helps, though I'm not sure what exactly that would tell you. Personally, heeding warnings that it would slow your system way down, I ran it over a telnet session from my NT laptop while getting other work done. I wasn't really paying attention to how long it took, though it seems like it might have been about 10 minutes or so. I'm running an old iMac Bondi Blue with a 233 mHz G3 processor & 64 mb of ram and both OS9 & OSX on the same partition.

I'm not really clear on what it did, but it took quite a while to do it. Whatever it was. If it only took a few seconds for you, I'd guess that nothing happened, and maybe nothing needs to happen. *shrug*

[ Reply to This | # ]