Date: Thu, 22 Aug 2002 04:44:41 -0700 From: Terry Lambert <tlambert2@mindspring.com> To: Mark Santcroos <marks@ripe.net> Cc: freebsd-current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: Memory corruption in CURRENT Message-ID: <3D64CEA9.8E6E3710@mindspring.com> References: <200208220909.g7M99NcS077303@freebsd.dk> <3D64B005.6657A3B5@mindspring.com> <20020822100014.GA17143@ripe.net> <3D64BA1F.B3C8C8E0@mindspring.com> <20020822102553.GA17453@ripe.net> <3D64C9C2.30A37BF8@mindspring.com> <20020822113411.GA23616@laptop.6bone.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
Mark Santcroos wrote: > I was just giving a slight report, not yelling halleluja yet ;-) > > It's doing the 2nd buildworld now. > > Do you also want me to try to split up the disabling of the two options? No. Me saying to use both options was just me being lazy about spending 2 days re-documenting the code from boot2 through mi_startup(), to be sure nothing had crept in there. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3D64CEA9.8E6E3710>