From owner-freebsd-current@FreeBSD.ORG Wed Jun 29 10:07:21 2005 Return-Path: X-Original-To: freebsd-current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CE94816A41C; Wed, 29 Jun 2005 10:07:21 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [204.156.12.53]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9FCC343D1D; Wed, 29 Jun 2005 10:07:21 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by cyrus.watson.org (Postfix) with ESMTP id 3094646B20; Wed, 29 Jun 2005 06:07:21 -0400 (EDT) Date: Wed, 29 Jun 2005 11:11:25 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Jeremie Le Hen In-Reply-To: <20050629083042.GB48704@obiwan.tataz.chchile.org> Message-ID: <20050629110805.W74117@fledge.watson.org> References: <20050626211011.GH1283@obiwan.tataz.chchile.org> <86d5q8113a.fsf@xps.des.no> <20050627130449.GQ1283@obiwan.tataz.chchile.org> <42C0026C.3040000@FreeBSD.org> <20050627191205.GT1283@obiwan.tataz.chchile.org> <1119900416.27663.15.camel@cream.xbsd.org> <20050629083042.GB48704@obiwan.tataz.chchile.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Dag-Erling =?iso-8859-1?Q?Sm=F8rgrav?= , freebsd-current@FreeBSD.org, freebsd-ports@FreeBSD.org Subject: Re: OpenPAM Figwort broke PAM modules from ports X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Jun 2005 10:07:21 -0000 On Wed, 29 Jun 2005, Jeremie Le Hen wrote: > Would you, or some other commiter, mind putting a note in src/UPDATING > about this please ? This doesn't cost too much while preventing users > from wasting time on understanding why their PAM module installed from > ports don't work any longer when they are not specified with their full > path. Could you propose specific text to add to UPDATING, and I'll drop it in? Perhaps something along the lines of the following: Some previous versions of PAM have permitted the use of non-absolute paths in /etc/pam.conf or /etc/pam.d/* when referring to third party PAM modules in /usr/local/lib. A change has been made to require the use of absolute paths in order to avoid ambiguity and dependence on library path configuration, which may affect existing configurations. Robert N M Watson