From owner-freebsd-stable@FreeBSD.ORG  Sat Jul 16 14:16:18 2005
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
X-Original-To: freebsd-stable@freebsd.org
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 4D95616A41C
	for <freebsd-stable@freebsd.org>; Sat, 16 Jul 2005 14:16:18 +0000 (GMT)
	(envelope-from mkb@mkbuelow.net)
Received: from luzifer.incubus.de (incubus.de [80.237.207.83])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 7ECFF43D45
	for <freebsd-stable@freebsd.org>; Sat, 16 Jul 2005 14:16:17 +0000 (GMT)
	(envelope-from mkb@mkbuelow.net)
Received: from drjekyll.mkbuelow.net (p54AA8609.dip0.t-ipconnect.de
	[84.170.134.9])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by luzifer.incubus.de (Postfix) with ESMTP id 58C7632A7B
	for <freebsd-stable@freebsd.org>; Sat, 16 Jul 2005 16:19:09 +0200 (CEST)
Received: from drjekyll.mkbuelow.net (mkb@localhost.mkbuelow.net [127.0.0.1])
	by drjekyll.mkbuelow.net (8.13.3/8.13.3) with ESMTP id j6GEGVVu000848
	for <freebsd-stable@freebsd.org>; Sat, 16 Jul 2005 16:16:31 +0200 (CEST)
	(envelope-from mkb@drjekyll.mkbuelow.net)
Received: (from mkb@localhost)
	by drjekyll.mkbuelow.net (8.13.3/8.13.3/Submit) id j6GEGUJ2000847
	for freebsd-stable@freebsd.org; Sat, 16 Jul 2005 16:16:30 +0200 (CEST)
	(envelope-from mkb)
Date: Sat, 16 Jul 2005 16:16:30 +0200
From: Matthias Buelow <mkb@incubus.de>
To: freebsd-stable@freebsd.org
Message-ID: <20050716141630.GB752@drjekyll.mkbuelow.net>
References: <20050715224650.GA48516@outcold.yadt.co.uk>
	<200507152342.j6FNg5Tx015427@drjekyll.mkbuelow.net>
	<20050716133710.GA71580@outcold.yadt.co.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20050716133710.GA71580@outcold.yadt.co.uk>
User-Agent: Mutt/1.4.2.1i
Subject: Re: dangerous situation with shutdown process
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, 
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 16 Jul 2005 14:16:18 -0000

David Taylor wrote:

>No.  I'm just asking if you know of ANY ata drives that will wait for the
>cache to be flushed before claiming the disable cache command has
>succeeded.  I don't, but I haven't looked.

I don't know either. I assume that they do. Does it matter?
I mean, I'm not suggesting a frivolous new theory that is highly
speculative and warrants a lengthy debate on its purported merits.
What I described is common practice on Windows, Linux and probably
a few other systems and I would think that they're not doing this
for nothing. And, frankly, I'm a bit astonished that the FreeBSD
(community) seems to be so ignorant of well-known measures for
improving data safety on consumer-grade desktop hardware. Does that
mean that FreeBSD is deemed generally unsuited for desktop and
laptop use and should be reserved for servers with the appropriate
(expensive) hardware? I hope not.

mkb.