From owner-freebsd-threads@FreeBSD.ORG Sun Jun 1 00:40:50 2003 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F2C9B37B404 for ; Sun, 1 Jun 2003 00:40:49 -0700 (PDT) Received: from segfault.kiev.ua (segfault.kiev.ua [193.193.193.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 641B343F85 for ; Sun, 1 Jun 2003 00:40:47 -0700 (PDT) (envelope-from netch@iv.nn.kiev.ua) Received: (from uucp@localhost) by segfault.kiev.ua (8) with UUCP id h617ehwu010958; Sun, 1 Jun 2003 10:40:43 +0300 (EEST) (envelope-from netch@iv.nn.kiev.ua) Received: (from netch@localhost) by iv.nn.kiev.ua (8.12.8p1/8.12.8) id h517dj1r005724; Sun, 1 Jun 2003 10:39:45 +0300 (EEST) (envelope-from netch) Date: Sun, 1 Jun 2003 10:39:45 +0300 From: Valentin Nechayev To: "Matthew D. Fuller" Message-ID: <20030601073945.GA5594@iv.nn.kiev.ua> References: <20030531024932.GP61246@over-yonder.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030531024932.GP61246@over-yonder.net> X-42: On Organization: Dark side of coredump cc: threads@freebsd.org cc: Daniel Eischen Subject: Re: Transition plans: libkse->libpthread X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Jun 2003 07:40:50 -0000 Fri, May 30, 2003 at 21:49:32, fullermd (Matthew D. Fuller) wrote about "Re: Transition plans: libkse->libpthread": >> Sometime shortly after 5.1 release, we'll (hopefully) be >> installing libpthread as "libpthread" instead of "libkse" >> by default. MDF> From my comfortable position here in the peanut gallery, I've been MDF> thinking about this. Now that we have libthr around (presumably for a MDF> long time), mightn't it be a good idea to keep libkse and libkse, libthr MDF> and libthr, and maybe even libc_r as libc_r, and have libpthread be a MDF> {sym,hard}link to one of the above? Since we're ending up with multiple MDF> libraries implementing the pthreads API, with the presumption that MDF> they're at least nominally interchangeable, might we not want to make MDF> that switchability explicit? I joined to this initially. But: 1. System-wide changing of, e.g., libkse to libthr in all applications, can be set up in libmap.conf. If system-wide libmap.conf is applicable by default to all binaries, including sugid ones, this will work. 2. Linker writes library specifications to binaries not with library name only, but with major number also. With libpthread as customized symlink, version bumps in all three libraries must be simultaneous and major numbers must be identical. With one default library, if libmap allows, any libpthread version can be mapped to any libthr or libc_r version. This is preferrable. So, I support installing libkse as libpthread using copy or (preferred) hard link. -netch-