From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/1695 Path: news.gmane.org!not-for-mail From: "Arvid E. Picciani" Newsgroups: gmane.linux.lib.musl.general Subject: Re: ldso: dlclose. Date: Thu, 23 Aug 2012 14:39:38 +0200 Message-ID: <5603ddad712718518eed1430f5d00450@exys.org> References: <503113C5.5010206@gmail.com> <20120820004803.GA27715@brightrain.aerifal.cx> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1345725596 30969 80.91.229.3 (23 Aug 2012 12:39:56 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 23 Aug 2012 12:39:56 +0000 (UTC) To: Original-X-From: musl-return-1696-gllmg-musl=m.gmane.org@lists.openwall.com Thu Aug 23 14:39:57 2012 Return-path: Envelope-to: gllmg-musl@plane.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by plane.gmane.org with smtp (Exim 4.69) (envelope-from ) id 1T4WhZ-0004JH-9g for gllmg-musl@plane.gmane.org; Thu, 23 Aug 2012 14:39:57 +0200 Original-Received: (qmail 26303 invoked by uid 550); 23 Aug 2012 12:39:55 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Original-Received: (qmail 26293 invoked from network); 23 Aug 2012 12:39:55 -0000 In-Reply-To: <20120820004803.GA27715@brightrain.aerifal.cx> X-Sender: aep@exys.org User-Agent: Roundcube Webmail/0.5.4 Xref: news.gmane.org gmane.linux.lib.musl.general:1695 Archived-At: On Sun, 19 Aug 2012 20:48:03 -0400, Rich Felker wrote: > To elaborate, removing a DSO from a process's address space is highly > non-trivial and error-prone. In fact it doesn't even work correctly in glibc. It's just that usually no one notices. When i see people using plugin architectures with unload, it's almost always coming down from a high level design. The lack of any usable IPC in linux lead to glueing the components into one process. Plugins make it appear clean, but really it's not clean at all. Much worse when C++ comes into the mix and arbitrary things happen at the "abi" level. Plugins are _not_ a good component separation design. Neither are any of the alternatives, of course... Another sad story of how the religious view of one kernel maintainer creates a whole universe of bad design further down. -- Arvid E. Picciani