From owner-freebsd-hackers Wed Apr 19 07:30:20 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id HAA20558 for hackers-outgoing; Wed, 19 Apr 1995 07:30:20 -0700 Received: from trout.sri.MT.net (trout.sri.MT.net [204.182.243.12]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id HAA20550 for ; Wed, 19 Apr 1995 07:30:16 -0700 Received: (from nate@localhost) by trout.sri.MT.net (8.6.11/8.6.11) id IAA03957; Wed, 19 Apr 1995 08:34:12 -0600 Date: Wed, 19 Apr 1995 08:34:12 -0600 From: Nate Williams Message-Id: <199504191434.IAA03957@trout.sri.MT.net> To: "Jordan K. Hubbard" Cc: Nate Williams , jmz@cabri.obs-besancon.fr (Jean-Marc Zucconi), hackers@FreeBSD.org Subject: Re: proposed change to ld.so In-Reply-To: <8105.798273116@freefall.cdrom.com> References: <199504190329.VAA01681@trout.sri.MT.net> <8105.798273116@freefall.cdrom.com> Sender: hackers-owner@FreeBSD.org Precedence: bulk > > To be honest, I have no idea how long this will take. I've been > > spending my time trying to understand the code and have spent little > > time with coding. I doubt anything will happen in the next week or so. > > What is causing the critical need for this? > > Certain impending release plans. I would be happy if you could just > commit it and proceed with your own work in parallel. Can do, but I'm not sure if the new code will affect the system in unforseen ways. I haven't tested the cascade code at all, and as we've all seen, even minor changes can cause major headaches. With the impending release, I felt it would be foolish to introduce something new into this critical part of the system. Nate