Date: Thu, 4 Sep 2014 10:05:24 +0200 From: u-igbb@...ey.se To: musl@...ts.openwall.com Subject: Re: libhybris and musl? > > IMHO this is how the shared libs concept should have been implemented > > from the very beginning. > > Not shared libs in general, but for "arbitrary pluggable modules to > inject into arbitrary programs to extend their functionality", yes. Indeed, it is using the shared libs technology for purposes where it is not a suitable tool which made it harmful. > Another clear example where this is needed is PAM. The idea of loading Sure, it was a brain-dead design from the beginning, otherwise also the nsswitch and even perl's and python's and gtk's ".so" modules and the non-GL X11 drivers too - the examples are unfortunately too numerous. Why do misleading concepts become so popular so easily? (NFS comes to mind as an impressive non-library example). Probably because they solve a problem of the day - who cares if they create a problem of a decennium or two... Sigh. Rune
Powered by blists - more mailing lists
Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.