From owner-freebsd-arch@FreeBSD.ORG Mon Jun 13 07:49:45 2005 Return-Path: X-Original-To: arch@freebsd.org Delivered-To: freebsd-arch@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 830D116A41C; Mon, 13 Jun 2005 07:49:45 +0000 (GMT) (envelope-from dfr@nlsystems.com) Received: from itchy.rabson.org (mailgate.nlsystems.com [80.177.232.242]) by mx1.FreeBSD.org (Postfix) with ESMTP id D061443D48; Mon, 13 Jun 2005 07:49:44 +0000 (GMT) (envelope-from dfr@nlsystems.com) Received: from herring.rabson.org (herring [10.0.0.2]) by itchy.rabson.org (8.13.3/8.12.11) with ESMTP id j5D7nQlb051881; Mon, 13 Jun 2005 08:49:26 +0100 (BST) (envelope-from dfr@nlsystems.com) From: Doug Rabson To: freebsd-arch@freebsd.org Date: Mon, 13 Jun 2005 08:49:25 +0100 User-Agent: KMail/1.8 References: <864qc9mgqc.fsf@xps.des.no> <42A75303.2090203@elischer.org> <42A75591.7080502@elischer.org> In-Reply-To: <42A75591.7080502@elischer.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200506130849.26026.dfr@nlsystems.com> X-Spam-Status: No, score=-2.8 required=5.0 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on itchy.rabson.org X-Virus-Scanned: ClamAV 0.83/934/Sun Jun 12 23:44:50 2005 on itchy.rabson.org X-Virus-Status: Clean Cc: Dag-Erling =?iso-8859-1?q?Sm=F8rgrav?= , Julian Elischer , arch@freebsd.org Subject: Re: Retiring static libpam support X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Jun 2005 07:49:45 -0000 On Wednesday 08 June 2005 21:31, Julian Elischer wrote: > adding more to my revious mail.. > > Julian Elischer wrote: > > Dag-Erling Sm=F8rgrav wrote: > >> Julian Elischer writes: > >>> I gues it would be ok if the basic binary is static and the PAM > >>> modules are loaded using dlopen. > >> > >> You can't load dynamic objects from a static binary. It doesn't > >> have a working dlopen() (since dlopen() is implemented by the > >> run-time loader), and even if it did, there is no relocation table > >> there to resolve dependencies in the dynamic object. > > > > so basically that would screw us. > > Or force us to abandon static linking of apps, > which might be an OK decision, but basically > I think it's kind of the thin edge of the wedge for fully > desupporting all static > binaries. if nothing that does authentication > can be static then there is no such thing any more as a fully static > system and one might as well just not bother. You can link statically to some libraries and dynamically to others -=20 that might work quite well. You would probably end up linking=20 dynamically to libc otherwise you might get two copies of libc when you=20 load a pam module.