From owner-freebsd-current Sun Dec 15 15:23:30 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA13825 for current-outgoing; Sun, 15 Dec 1996 15:23:30 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id PAA13783 for ; Sun, 15 Dec 1996 15:23:24 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id AAA23108; Mon, 16 Dec 1996 00:22:49 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id AAA03219; Mon, 16 Dec 1996 00:22:48 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id AAA01712; Mon, 16 Dec 1996 00:15:43 +0100 (MET) From: J Wunsch Message-Id: <199612152315.AAA01712@uriah.heep.sax.de> Subject: Re: Plan for integrating Secure RPC -- comments wanted To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Mon, 16 Dec 1996 00:15:42 +0100 (MET) Cc: wpaul@skynet.ctr.columbia.edu (Bill Paul) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199612152022.PAA05216@skynet.ctr.columbia.edu> from Bill Paul at "Dec 15, 96 03:22:39 pm" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Bill Paul wrote: > Splitting out the DES code > --------------------------- > Right now, there are several programs in /bin and /sbin which use > NIS code as a side effect of calling libc functions that have NIS > support in them. All the executables in these directories are linked > The question then is how to seperate out the DES code without actually > changing any executables. There are actually three ways, all of which > suck. It's a matter of choosing the least suckiest. Why not using explicit dynamic linking for this? (dlopen(3)) Since you can concentrate on a single library entry point, this should be not too complicated. The point is that you try to load the shared lib only if an actual call is made to it, rather then loading every- thing before the executable starts. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)