From owner-freebsd-stable Thu May 7 14:15:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA06432 for freebsd-stable-outgoing; Thu, 7 May 1998 14:15:56 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dt050n33.san.rr.com (@dt053nd2.san.rr.com [204.210.34.210]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA06275; Thu, 7 May 1998 14:14:47 -0700 (PDT) (envelope-from Studded@san.rr.com) Received: from san.rr.com (Studded@localhost [127.0.0.1]) by dt050n33.san.rr.com (8.8.8/8.8.8) with ESMTP id OAA01168; Thu, 7 May 1998 14:14:35 -0700 (PDT) (envelope-from Studded@san.rr.com) Message-ID: <3552243B.15AAF366@san.rr.com> Date: Thu, 07 May 1998 14:14:35 -0700 From: Studded Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 2.2.6-STABLE-0507 i386) MIME-Version: 1.0 To: Craig Wilson CC: freebsd-stable@FreeBSD.ORG, phk@FreeBSD.ORG, dg@root.com Subject: Re: FreeBSD 2.2.6-RELEASE References: <35502381.7A27@natsoft.com.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk Craig Wilson wrote: > > I am currently using FreeBSD 2.2.2-RELEASE in several commercial sites, > ie running companies accounting and point of sale systems. I have > found FreeBSD 2.2.2 very stable, however would like to use 2.2.6. > I am not in a position to use CVS or to make worlds etc, because > of the number of commercial sites I have, approx 25, some of which > are required to run 24 hours a day, I simply install from CD-ROM, > apply a few patches, and then leave the computer alone. > > Could somebody please tell me whether the fixes to the following problem > reports made it into FreeBSD 2.2.6-RELEASE, and if they did not make > it what the fixes are, and whether the problems are serious and need > fixing. Also are there any other problems that should be fixed with > FreeBSD 2.2.6-RELEASE before putting it into a commercial situation. > > kern/4844 VM lookup, endless loop in vm_map_lookup_lookup_entry() > this PR was closed on Apr26 1998 Poul was the one who closed this with "fixed in -current." He's the one who should be able to tell you if it's fixed in -stable. Given that 2.2.6-Release was cut in march, this PR is certainly not fixed in that release. > kern/6258 VM lookup on kernel map........ > this PR was closed on Apr26 1998 Similar situation with this one, fixed after 2.2.6-Release. It's also closed by poul with "fixed in -current" in spite of the fact that the audit trail has David Greenman asking for the fix to be applied to -Stable. Hope this is helpful to you, Doug -- *** Chief Operations Officer, DALnet IRC network *** *** Proud designer and maintainer of the world's largest Internet *** Relay Chat server with 5,328 simultaneous connections. *** Try spider.dal.net on ports 6662-4 (Powered by FreeBSD) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message