From owner-freebsd-arch@FreeBSD.ORG  Wed Apr 13 16:49:38 2005
Return-Path: <owner-freebsd-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 CE18C16A4CE; Wed, 13 Apr 2005 16:49:38 +0000 (GMT)
Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 5AACB43D1D; Wed, 13 Apr 2005 16:49:38 +0000 (GMT)
	(envelope-from scottl@samsco.org)
Received: from [166.220.248.152] (DEN-166-220-248-152.goport.net
	[166.220.248.152] (may be forged))	(authenticated bits=0)
	by pooker.samsco.org (8.13.1/8.13.1) with ESMTP id j3DGpTwe046097;
	Wed, 13 Apr 2005 10:51:29 -0600 (MDT)
	(envelope-from scottl@samsco.org)
Message-ID: <425D4C90.9090702@samsco.org>
Date: Wed, 13 Apr 2005 10:45:04 -0600
From: Scott Long <scottl@samsco.org>
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: "M. Warner Losh" <imp@bsdimp.com>
References: <425D2041.7020501@samsco.org>
	<20050413.085652.56562781.imp@bsdimp.com>
In-Reply-To: <20050413.085652.56562781.imp@bsdimp.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Status: No, score=0.0 required=3.8 tests=none 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: davidxu@freebsd.org
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
	<freebsd-arch.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arch>
List-Post: <mailto:freebsd-arch@freebsd.org>
List-Help: <mailto:freebsd-arch-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Apr 2005 16:49:38 -0000

M. Warner Losh wrote:
> In message: <425D2041.7020501@samsco.org>
>             Scott Long <scottl@samsco.org> writes:
> : 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?
> 
> I'd do a build-time warning only.
> 
> This would allow poeple to deploy systems with libc_r and not have
> annoying warnings at a customer's site.  They will know that things
> are deprecated.  Also, compat librarires will be around for a while,
> so doing things at runtime seems annoying...
> 
> As far as my company's use of libc_r, we don't yet know how well
> non-libc_r works yet since we've not done any large threaded FreeBSD 5
> applications yet.  So I can't comment on how wise/foolish this option
> is with any direct experience.
> 
> Warner

Yes, outfits like yours and Julian's are exactly what I had in mind when 
I said that it would be several years before it goes away, and even then
it would live on in /usr/lib/compat.

Scott