From owner-freebsd-current Sun Dec 17 22:26:19 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id WAA06456 for current-outgoing; Sun, 17 Dec 1995 22:26:19 -0800 (PST) Received: from grunt.grondar.za (grunt.grondar.za [196.7.18.129]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id WAA06449 Sun, 17 Dec 1995 22:26:07 -0800 (PST) Received: from grumble.grondar.za (root@grumble.grondar.za [196.7.18.130]) by grunt.grondar.za (8.6.12/8.6.9) with ESMTP id IAA04837; Mon, 18 Dec 1995 08:26:02 +0200 Received: from localhost (mark@localhost [127.0.0.1]) by grumble.grondar.za (8.7.3/8.6.9) with SMTP id IAA26327; Mon, 18 Dec 1995 08:26:01 +0200 (SAT) Message-Id: <199512180626.IAA26327@grumble.grondar.za> X-Authentication-Warning: grumble.grondar.za: Host mark@localhost [127.0.0.1] didn't use HELO protocol To: davidg@Root.COM cc: sos@freebsd.org, current@freebsd.org, hacker@freebsd.org Subject: Re: FreeBSD-current-stable ??? Date: Mon, 18 Dec 1995 08:25:59 +0200 From: Mark Murray Sender: owner-current@freebsd.org Precedence: bulk David Greenman wrote: > >> >I run -currrent (up until last week) on my machine at TFS.com > >> >and I have had NO troubles with it... > >> > >> I have had only one serious problem (2 core dumps apparently caused by > >> some vm change in the last month). > > > >You must have another current than most of us :) :) > > Actually, I haven't had any problems with -current, either. Just another data point for this graph; I had about 2 weeks of hassles while a make world would not complete without a bit of help, and then 2 days of a messed kernel (some was fixed as soon as I reported it (KERNFS)). It has been more stable, but for me it has not been as bad as it seems for some folks. OTOH, when I see lots of problem repots that are out of my league, I back off and wait for the appropriate commits :-> :-> M -- Mark Murray 46 Harvey Rd, Claremont, Cape Town 7700, South Africa +27 21 61-3768 GMT+0200 Finger mark@grondar.za for PGP key