From owner-freebsd-hackers Sat Mar 22 15:12:16 2003 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7A69F37B404 for ; Sat, 22 Mar 2003 15:12:15 -0800 (PST) Received: from lilzcluster.liwest.at (lilzclust01.liwest.at [212.33.55.11]) by mx1.FreeBSD.org (Postfix) with ESMTP id E7DFC43F3F for ; Sat, 22 Mar 2003 15:12:13 -0800 (PST) (envelope-from dgw@liwest.at) Received: from CM58-27.liwest.at by lilzcluster.liwest.at (8.10.2/1.1.2.11/08Jun01-1123AM) id h2MNAuV0000771634; Sun, 23 Mar 2003 00:10:56 +0100 (MET) Content-Type: text/plain; charset="iso-8859-1" From: Daniela To: Kris Kennaway Subject: Re: Lots of kernel core dumps Date: Sun, 23 Mar 2003 00:10:38 +0100 User-Agent: KMail/1.4.3 Cc: hackers@FreeBSD.ORG References: <200303212037.46322.dgw@liwest.at> <200303212226.01853.dgw@liwest.at> <20030321221514.GA24787@rot13.obsecurity.org> In-Reply-To: <20030321221514.GA24787@rot13.obsecurity.org> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Message-Id: <200303230010.38736.dgw@liwest.at> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > I know, but 5.0-RELEASE was > > a) A work-in-progress, not a perfect, bug-free release > > b) A snapshot of 5.0-CURRENT > > You read the 5.0 Early Adopter's Guide, right? Bugs like this are > expected at this stage in the development process, and if you > encounter them then you need to either give up on 5.x and go back to > 4.x-STABLE, or upgrade to 5.0-CURRENT if they are already fixed there. > > Kris Yes, I read the Early Adopter's Guide. Is there any way to solve this without upgrading to -current? I want a stable server, of course, but I still want to help the FreeBSD f= olks=20 to make 5.0 the best release ever. This requires testing to be done. Daniela To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message