From owner-freebsd-hackers Sun Jun 23 11:18:10 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from utility.clubscholarship.com (utility.clubscholarship.com [198.78.70.175]) by hub.freebsd.org (Postfix) with ESMTP id 6AD5837B404 for ; Sun, 23 Jun 2002 11:18:06 -0700 (PDT) Received: from localhost (root@localhost) by utility.clubscholarship.com (8.11.6/8.11.6) with ESMTP id g5NIDoP16843; Sun, 23 Jun 2002 11:14:06 -0700 (PDT) (envelope-from root@utility.clubscholarship.com) Date: Sun, 23 Jun 2002 11:13:50 -0700 (PDT) From: Patrick Thomas To: Terry Lambert Cc: Joshua Lee , Subject: Re: inuring FreeBSD to the apache bug without upgrading apache ? In-Reply-To: <3D15BBE1.83E4DCF7@mindspring.com> Message-ID: <20020623111107.F68572-100000@utility.clubscholarship.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Yeah; this whole thread is premised on working around the > problem without an Apache software change. It's a reasonable > premise (IMO) -- if you've got a custom compilation and a lot > of modules, that can end up being a lot of software. I build > a PHP4+SSL+Apache+IMAP+etc. source tree at one point, and it > ended up being ~1.2 million lines of code, all told, that had > to be made to work together. If you had "just built it", then > it would be very hard to update just one component without > repeating the whole process. My advice? Use CVS. Actually, this whole thread is premised on I have a dev system with 16 jailed apaches and it would be a pain to upgrade all 16 of them vs. just making one global kernel/environment change. It sounds like that is probably a pipe dream though.. --PT To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message