From owner-freebsd-hackers Fri Mar 10 08:13:34 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA17428 for hackers-outgoing; Fri, 10 Mar 1995 08:13:34 -0800 Received: from sbstark.cs.sunysb.edu (sbstark.cs.sunysb.edu [130.245.1.47]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id IAA17422 for ; Fri, 10 Mar 1995 08:13:33 -0800 Received: from starkhome.UUCP (root@localhost) by sbstark.cs.sunysb.edu (8.6.9/8.6.9) with UUCP id LAA24721 for hackers@freebsd.org; Fri, 10 Mar 1995 11:13:34 -0500 Received: by starkhome.cs.sunysb.edu (8.6.10/1.34) id LAA10243; Fri, 10 Mar 1995 11:12:55 -0500 Date: Fri, 10 Mar 1995 11:12:55 -0500 From: starkhome!gene@sbstark.cs.sunysb.edu (Gene Stark) Message-Id: <199503101612.LAA10243@starkhome.cs.sunysb.edu> To: Morgan Davis CC: hackers@FreeBSD.org In-reply-to: Morgan Davis's message of Fri, 10 Mar 1995 01:57:48 -0800 (PST) Subject: Re: SNAP or current? Sender: hackers-owner@FreeBSD.org Precedence: bulk >At which point in time did you see all these problems start occuring? >I just grabbed -current (previoustime was about Feb 10). I'm >wondering if these are problems you've had for a long time or ones >that have recently plagued your system. (This'll determine whether or >not I'll build and install the 3/10 -current and kernel). I have a source tree from Jan 31 which is very stable. I have had uptimes of over 30 days with a kernel from that one. A kernel I made on Feb 17 also seemed to be reasonable, thought I thing the "gdb crash" problem is in that one. Apparently serious problems were introduced mostly during mid-to late February. Or, the problems that were already there were unmasked by other changes. - Gene