From owner-freebsd-current Tue Mar 10 19:10:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA02580 for freebsd-current-outgoing; Tue, 10 Mar 1998 19:10:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA02575 for ; Tue, 10 Mar 1998 19:10:10 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id TAA06520 for ; Tue, 10 Mar 1998 19:03:40 -0800 (PST) Received: from UNKNOWN(), claiming to be "current1.whistle.com" via SMTP by alpo.whistle.com, id smtpd006516; Tue Mar 10 19:03:33 1998 Message-ID: <3505FE01.695678E2@whistle.com> Date: Tue, 10 Mar 1998 18:59:13 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2.5-RELEASE i386) MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: Softupdates code not Prime Time yet. Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is to let those of you who are looking a the soft-updates code, know that there are still several known problems with the code. We have 2 (possibly but not neccesarily related) crash scenarios, and also a dependency tracking failure. The latter means that there are cases (hey let's be real, USUALLY) where a crash with softupdates running on an active filesystem, will have similar corrupting actions as running async (or at least sync) at the time of a crash. This is a BUG (unlike in async where it is a feature :-) and we are trying to find the missing dependency. So while it's good to play with and really fast, it should still be only used on replaceable data (e.g. /usr/obj) Thanks for all the testing and support! julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message