From owner-freebsd-arch@FreeBSD.ORG Wed Apr 13 14:47:08 2005 Return-Path: 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 51FA716A4CE; Wed, 13 Apr 2005 14:47:08 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id D5DD143D6D; Wed, 13 Apr 2005 14:47:07 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (junior-wifi.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.1/8.13.1) with ESMTP id j3DEoGhl045346; Wed, 13 Apr 2005 08:50:17 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <425D302C.1060006@samsco.org> Date: Wed, 13 Apr 2005 08:43:56 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.5) Gecko/20050218 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Poul-Henning Kamp References: <19268.1113403507@critter.freebsd.dk> In-Reply-To: <19268.1113403507@critter.freebsd.dk> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.8 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on pooker.samsco.org cc: arch@freebsd.org cc: re@freebsd.org cc: Giorgos Keramidas cc: David Xu Subject: Re: HEADS-UP: Planning on deprecating libc_r for 6.0 X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Apr 2005 14:47:08 -0000 Poul-Henning Kamp wrote: > In message <20050413144159.GA40749@orion.daedalusnetworks.priv>, Giorgos Keramidas writes: > >>On 2005-04-13 07:36, Scott Long wrote: >> >>>All, >>> >>>Now that we've had working KSE for 2 years, I'm planning to declare that >>>libc_r will be deprecated in 6.0 [...] >>> >>>One question that has come up is how to warn the user at runtime about >>>this deprecation. Should the dynamic linker print a message to stderr >>>when it gets a request to load libc_r? Should it go to the console >>>and/or syslog instead? Should there be a way to disable these messages >>>so as not to break wrapper programs that might be confused by the >>>output? Should we even bother at all with runtime warnings? >> >>How about modifying the dynamic linker to print a warning to stderr, >>much like mktemp(3), but let the user disable it by setting an >>environment variable, like LD_WARN_LIBC_R_DISABLE or similar? > > > The user can disable it by adding a line in libmap.conf so let us > not invent more handles to tweak but point the user at the right > one. > Well, the worry is that there are legacy apps out there that rely on features/bugs only found in libc_r, therefore the user can't just switch. Scott