Re: question regarding prelinking (was: (inc. note from dpkg developers) (was: Bug#XXXXXX: (far too many packages) needs rebuilt for prelinking))
On Tue, Jan 14, 2003 at 12:12:39PM -0800, Craig Dickson wrote:
> Daniel Jacobowitz wrote:
>
> > Prelinking depends on the entire, and exact, library set on a system.
> > The symbol offsets vary in most builds of a library; it's much
> > finer-grained than ABI-compatibility. The selected address ranges
> > depend on how many other libraries you have installed.
> >
> > If prelinking fails at runtime, the linker will handle it gracefully;
> > but it's slow and generally undesirable. Also, we lose the --verify
> > functionality; there's no way to reproduce the "previous" prelinking
> > state.
>
> Okay, I think I have a grasp of this prelinking idea now, at least in
> principle. It sounds like a nice little performance enhancement to have
> on a machine that doesn't change much, but how do you keep things in
> sync on a testing or unstable system? Is there a database that keeps
> track of what's prelinked to what, system-wide, so you can minimally
> re-prelink those files that are affected by an upgrade of some library?
> Or do you just re-prelink the entire system after each apt-get
> (dist-)upgrade? Or do programs just start more slowly after an upgrade
> until a cron job fixes everything up at 4 AM?
I don't know :) Probably (b) is the most common use case.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
Reply to: