On Friday 04 April 2003 00:37, Jakub Jelinek uttered: > The way IMHO prelink should work is from a cron job, say nightly, > either checking if any package has been installed in the last day > and if so, run prelink in the --fast mode (to be implemented yet), > which would just check timestamps of all libraries and binaries > in the database and redo only what changed since last time. > Maybe weekly it could do a normal full blown prelink checking, > to catch manually installed programs/libraries etc. > (Note --fast mode is only planned, not implemented yet). > > The reason why it is not enabled in Shrike is that it was not enabled > early enough in the beta cycle (at that point prelink did not work > with TLS in libc, so could not be enabled). > I hope we'll enable it in the next beta cycle. Is there some documentation somewhere on prelink, and what it gains the end user? -- Jesse Keating RHCE MCSE http://geek.j2solutions.net Mondo DevTeam (www.mondorescue.org) Was I helpful? Let others know: http://svcs.affero.net/rm.php?r=jkeating
