From owner-freebsd-hackers Thu Mar 9 22:47:22 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id WAA07196 for hackers-outgoing; Thu, 9 Mar 1995 22:47:22 -0800 Received: from Root.COM (implode.Root.COM [198.145.90.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id WAA07187 for ; Thu, 9 Mar 1995 22:47:19 -0800 Received: from corbin.Root.COM (corbin.Root.COM [198.145.90.18]) by Root.COM (8.6.8/8.6.5) with ESMTP id WAA02045; Thu, 9 Mar 1995 22:47:12 -0800 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.9/8.6.5) with SMTP id WAA00156; Thu, 9 Mar 1995 22:47:12 -0800 Message-Id: <199503100647.WAA00156@corbin.Root.COM> X-Authentication-Warning: corbin.Root.COM: Host localhost didn't use HELO protocol To: Gary Roberts cc: hackers@FreeBSD.org Subject: Re: SNAP or current? In-reply-to: Your message of "Fri, 10 Mar 95 16:32:15 +1000." <9503100632.AA26647@wcs.uq.edu.au> From: David Greenman Reply-To: davidg@Root.COM Date: Thu, 09 Mar 1995 22:47:12 -0800 Sender: hackers-owner@FreeBSD.org Precedence: bulk >Poul-Henning Kamp writes: > >> > is anyone likely to roll a new SNAP? Just curious ... >> belive me, I'm trying .... > >Great!! I've got someone who is running a lab with about 20 Linux boxes >who is keen to give FreeBSD a spin. A nice stable SNAP would be perfect. Umm, I wouldn't count on the next SNAP being too stable. I have a dozen serious bugs (panics or system hangs) on the whiteboard, and I don't expect to have more than one or two of them fixed before the next SNAP. I wish I could be more positive, but I've been working on finding some of these bugs for several weeks. They take the form of random corruption of kernel memory with nearly random data...and aren't reproducible. -DG