Wittams on Shared Libraries
Jonathan S. Shapiro
Sat, 8 Jul 2000 20:40:55 -0400
> It also avoids the pitfal that Kragen mentioned in chroot. The builder
> of the app gets to choose the library, not merely its name!
This is both a strength and a weakness. It means that you know what code is
running, but it also makes upgrade hard. I am inclined to think that
intermediation is useful here. Code should not be updated without
application consent, but there should be a mechanism to support such
Add this to the list of pending design challenges.