Samuel Greenfeld greenfeld at
Wed May 18 09:51:33 EDT 2011

In general every major Fedora jump we do risks running out of space.  In
addition to upgrades, they also did a mass recompile for the upcoming F15
release.  As long as we use a hardlink/multiple-root/rsync approach, I do
not see an easy answer to this.

What seems to be missing (in this discussion, and perhaps in the utility) is
support in the OS builder to incrementally update based on a previous
build.  Prelink is capable of keeping a cache of what was previously done,
and running in an incremental mode where only the necessary binaries are

This would solve much of the grief with minor updates, where we only pull in
selected RPMs.

An alternative which might be even less disruptive would be to run prelink
on 11.2.0, and use that image as the base to create future 11.2.x, builds.
We would then tolerate collisions due to updates pulled in past that point.
This has the downside though that changing something low level like glibc
could result in an across-the-board performance penalty.

On Wed, May 18, 2011 at 8:13 AM, Paul Fox <pgf at> wrote:

> james wrote:
>  > On Wed, May 18, 2011 at 07:45:49AM -0400, Kevin Gordon wrote:
>  > > Might be over my head in the specific prelink OLPC talk here, but in
>  > > my experience on the iSeries - anything that optimizes a software
>  > > update process (which happens twice a year) at the expense of a
>  > > program loads or the object instantiation process (which happen
>  > > thousands of times an hour) is a bad trade-off.
>  >
>  > +1
> but unless i misunderstood dsd, prelink is making our update process
> non-functional.
> paul
> =---------------------
>  paul fox, pgf at
> _______________________________________________
> Devel mailing list
> Devel at
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the Devel mailing list