From owner-cvs-all Tue Dec 7 23:37:48 1999 Delivered-To: cvs-all@freebsd.org Received: from ind.alcatel.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (Postfix) with ESMTP id 95CF814D12; Tue, 7 Dec 1999 23:37:45 -0800 (PST) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com (mailhub [198.206.181.70]) by ind.alcatel.com (8.9.3+Sun/8.9.1 (ind.alcatel.com 3.0 [OUT])) with SMTP id XAA00261; Tue, 7 Dec 1999 23:37:13 -0800 (PST) X-Origination-Site: Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id XAA01348; Tue, 7 Dec 1999 23:37:13 -0800 Received: from softweyr.com ([204.68.178.39]) by omni.xylan.com (4.1/SMI-4.1 (xylan engr [SPOOL])) id AA05227; Tue, 7 Dec 99 23:37:09 PST Message-Id: <384E0ACA.BBCA08C0@softweyr.com> Date: Wed, 08 Dec 1999 00:37:46 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.61 [en] (X11; I; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en Mime-Version: 1.0 To: mjacob@feral.com Cc: Mike Smith , cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/kern kern_shutdown.c References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk Matthew Jacob wrote: > > > > Yes, it is in fact. If you cannot guarantee data integrity, you shouldn't > > > be running on it. If you have to run on it, don't expect data integrity. > > > > I thought your argument was "we ought to work properly where it's > > possible, rather than pursue some golden ideal of perfection"? > > No- not quite. We should claim to support sane hardware, but shrug and > hand the user the bullets if they want to end it all for themselves. Some of those oddball drives (like Zip) can be quite beneficial for certain applications. When you need ~100 MBytes of storage, there aren't many cheaper ways to get it than a Zip drive. Reliability? Well, it has some. > > > (okay, so it's a couple of buffers at shutdown- in any case, perhaps the > > > driver that sees Synchronize Cache not working should do something else- > > > maybe calculate the Pareto for the first occurence of a y3k bug) > > > > You could just delay for a couple of seconds and guarantee that even if > > the Synchronise Cache command didn't work, the drive will still have > > flushed it's cache. Oops, looks like that's what I committed the other > > day. > > You're toying with me, aren't you? Yes, Mike enjoys that sort of sport. ;^) -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message