From owner-freebsd-current@FreeBSD.ORG Tue Nov 25 15:42:11 2003 Return-Path: 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 1491A16A4D3 for ; Tue, 25 Nov 2003 15:42:10 -0800 (PST) Received: from smtp1.server.rpi.edu (smtp1.server.rpi.edu [128.113.2.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id A135B4406C for ; Tue, 25 Nov 2003 15:41:19 -0800 (PST) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by smtp1.server.rpi.edu (8.12.10/8.12.9) with ESMTP id hAPNfH7P028907; Tue, 25 Nov 2003 18:41:18 -0500 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: References: <20031125025621.453732A8FC@canning.wemm.org> <20031125150700.GA48007@madman.celabo.org> <200311251950.hAPJoPoo080586@apollo.backplane.com> Date: Tue, 25 Nov 2003 18:41:16 -0500 To: Brad Knowles From: Garance A Drosihn Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Scanned-By: CanIt (www . canit . ca) cc: freebsd-current@freebsd.org Subject: Re: 40% slowdown with dynamic /bin/sh X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Tue, 25 Nov 2003 23:42:12 -0000 At 11:27 PM +0100 11/25/03, Brad Knowles wrote: >At 11:50 AM -0800 2003/11/25, Matthew Dillon wrote: > >> ... Or you can build an IPC mechanism that implements >> the PAM functionality and then have programs which >> would otherwise use PAM instead use the IPC mechanism. >> Which is the whole point of having the IPC mechanism >> in the first place. > > That all sounds wonderful! > > So, when are you going to deliver this fully functioning >and debugged code for inclusion in FreeBSD-5.2? My guess is that he will deliver it to DragonFly BSD, and it will then be up to someone with FreeBSD commit privs to look at steal^h^h^h^h^h^h adapting it for our purposes... Note that we are already in the code-freeze for 5.2-release, so I will estimate the probability that all this happens in time for this release is zero. Absolute zero. What might happen for 5.3-release is a different story, of course. -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu