From owner-freebsd-stable@FreeBSD.ORG Tue Jul 19 03:31:07 2005 Return-Path: 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 6A87716A41C for ; Tue, 19 Jul 2005 03:31:07 +0000 (GMT) (envelope-from rees@ddcom.co.jp) Received: from proxy.ddcom.co.jp (proxy.ddcom.co.jp [211.121.191.163]) by mx1.FreeBSD.org (Postfix) with SMTP id BB04E43D45 for ; Tue, 19 Jul 2005 03:31:06 +0000 (GMT) (envelope-from rees@ddcom.co.jp) Received: (qmail 32686 invoked by alias); 19 Jul 2005 03:40:38 -0000 Received: from unknown (HELO ?172.16.1.133?) (10.10.10.11) by mail.ddcom.local with SMTP; 19 Jul 2005 03:40:38 -0000 Mime-Version: 1.0 (Apple Message framework v730) In-Reply-To: <20050715210320.01E215D07@ptavv.es.net> References: <20050715210320.01E215D07@ptavv.es.net> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <30C8CD81-73BF-4823-9B41-E8DA23F1EC43@ddcom.co.jp> Content-Transfer-Encoding: 7bit From: Joel Rees Date: Tue, 19 Jul 2005 12:30:12 +0900 To: freebsd-stable@freebsd.org X-Mailer: Apple Mail (2.730) 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Jul 2005 03:31:07 -0000 Comment from out in left field -- On 2005/07/16, at 6:03, Kevin Oberman wrote: > [...] > I believe that the Windows solution to this problem is to put a > really, > really long delay between when the system is finished syncing and when > the power is turned off. That's what I vote for. If the system has ATA on it, send a line to the console that says waiting for ATA technology drives to quit lying after the final sync, and then wait 30 seconds to cut power. > This might be the best solution for FreeBSD, as > well, but it will irritate people. My impression is that in this case irritation is recommended. (I'm half wondering if Microsoft and the drive manufacturer's haven't defined some hidden API for forcing the drive electronics to be truthful.)