From owner-freebsd-current Thu Nov 7 9:17:46 2002 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 3A73537B401 for ; Thu, 7 Nov 2002 09:17:45 -0800 (PST) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id CC97243E3B for ; Thu, 7 Nov 2002 09:17:44 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.12.6/8.12.6) with ESMTP id gA7HHf8A041340; Thu, 7 Nov 2002 09:17:41 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.12.6/8.12.6/Submit) id gA7HHfZc041339; Thu, 7 Nov 2002 09:17:41 -0800 (PST) Date: Thu, 7 Nov 2002 09:17:41 -0800 From: Steve Kargl To: John Polstra Cc: current@FreeBSD.ORG, imp@bsdimp.com Subject: Re: [PATCH] note the __sF change in src/UPDATING Message-ID: <20021107171741.GA41290@troutmask.apl.washington.edu> References: <200211070030.gA70UF05024508@troutmask.apl.washington.edu> <20021106.231940.123343134.imp@bsdimp.com> <200211071640.gA7GeWJk065460@vashon.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200211071640.gA7GeWJk065460@vashon.polstra.com> User-Agent: Mutt/1.4i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Nov 07, 2002 at 08:40:32AM -0800, John Polstra wrote: > In article <20021106.231940.123343134.imp@bsdimp.com>, > M. Warner Losh wrote: > > In message: <200211070030.gA70UF05024508@troutmask.apl.washington.edu> > > "Steven G. Kargl" writes: > > : Could someone add the following patch to UPDATING? > > : Change the words to whatever suits your fancy. > > > > I'm trying to devise a good way to deal with this breakage and hope it > > is transient. I'm not hopeful :-( I'll consider adding this to UPDATING. > > FWIW, the only OS fix that will make stock ezm3/pm3/CVSup buildable on > -current is to make __sF global again and arrange for: > > stdin == &__sF[0] > stdout == &__sF[1] > stderr == &__sF[2] > John, As the author of cvsup, I'm sure you know what is required. But, I rebuilt cvsup from net/cvsup yesterday on a new world, and it appears to be working fine. What problems should I expect? -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message