From owner-freebsd-current Sun May 3 00:54:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA24674 for freebsd-current-outgoing; Sun, 3 May 1998 00:54:08 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from thelab.hub.org (tc-7.acadiau.ca [131.162.2.107]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA24666 for ; Sun, 3 May 1998 00:54:04 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.8.8/8.8.2) with SMTP id EAA11185; Sun, 3 May 1998 04:53:41 -0300 (ADT) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Sun, 3 May 1998 04:53:41 -0300 (ADT) From: The Hermit Hacker To: "John S. Dyson" cc: andrew@iaccess.com.au, current@FreeBSD.ORG Subject: Re: Apache and -current kernel ... appears to work ... In-Reply-To: <199805030316.WAA00564@dyson.iquest.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 2 May 1998, John S. Dyson wrote: > I know about one significant bug in the -current kernel, and I can reproduce > it at will. It has been elusive so far, but should be a simple fix. I am > relentlessly attacking it right now. How? I'm building this machine for production use, knowing full well what I'm getting myself into...am curious as to whether the bug is something I could possibly trip over accidently :) Marc G. Fournier Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message