2) normally, when 5 running binaries use the same library, there is only
one copy of that library in memory. However, when a library gets
prelinked, a *new copy* of that library is put on disk (one with all the
prelink information), and new binaries that start and use that library
won't and cannot share it with the existing running binaries, so this
leads to temporarily increased real memory usage (temporary because
eventually all apps that use keep the old libs "in use" exit and only
"new library" applications are running). The exception can be very long
running applications (like cron.weekly) which now have library stuff
that is hardly ever used and the VM subsystem may choose to swap some of
that out.