Date: Thu, 7 Nov 2002 09:17:41 -0800 From: Steve Kargl <sgk@troutmask.apl.washington.edu> To: John Polstra <jdp@polstra.com> 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> In-Reply-To: <200211071640.gA7GeWJk065460@vashon.polstra.com> References: <200211070030.gA70UF05024508@troutmask.apl.washington.edu> <20021106.231940.123343134.imp@bsdimp.com> <200211071640.gA7GeWJk065460@vashon.polstra.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Nov 07, 2002 at 08:40:32AM -0800, John Polstra wrote: > In article <20021106.231940.123343134.imp@bsdimp.com>, > M. Warner Losh <imp@bsdimp.com> wrote: > > In message: <200211070030.gA70UF05024508@troutmask.apl.washington.edu> > > "Steven G. Kargl" <kargl@troutmask.apl.washington.edu> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021107171741.GA41290>