Date: Thu, 19 Apr 2001 18:20:59 -0700 From: Brian Tiemann <briant@packeteer.com> To: Kris Kennaway <kris@obsecurity.org> Cc: Rob Simmons <rsimmons@wlcg.com>, Ben Vaughn <bvaughn@BlackbirdTech.com>, Chris Faulhaber <jedgar@fxp.org>, security@FreeBSD.ORG Subject: Re: Another glob problem Message-ID: <3ADF8EFB.1B6EBA04@packeteer.com> References: <20010419164947.M72854-100000@mail.wlcg.com> <3ADF7BDD.A7868DA@packeteer.com> <20010419180118.C54774@xor.obsecurity.org> <3ADF8C73.7E987982@packeteer.com> <20010419181459.B57373@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Yes, I cvsupped immediately before rebuilding. That's the entire problem. The current best attempt has been to remove /usr/src and /usr/obj, cvsup to checkout a fresh 4-STABLE tree as of this afternoon, and try to build libc. But that's not working. So while what's causing libc to not compile is probably not related to the patch, what it means is that we're all effectively left without a solution to the ftpd overflow problem until the build error in mpool.c is dealt with. I cvsup 4-STABLE every night. I sort of thought that was what "tracking -STABLE" meant. It's so I don't have to worry about downloading patches. Brian Kris Kennaway wrote: > > On Thu, Apr 19, 2001 at 06:10:11PM -0700, Brian Tiemann wrote: > > Well, that's great, but something needs to be looked at for those of us > > tracking 4-STABLE. Thanks... > > If you're tracking -stable, why not just cvsup? We can't possibly > test the patches with every possible different point on the RELENG_4 > continuum, so we kind of assume that if you've cvsupped once to get to > a non-release version of -stable you can do it again. Having said > that, I can't think of any differences in libc which would have caused > this to fail between 4.2-REL and some later version of 4.2-STABLE. > > Kris > > ------------------------------------------------------------------------ > Part 1.2Type: application/pgp-signature To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3ADF8EFB.1B6EBA04>