From owner-freebsd-current@FreeBSD.ORG Fri May 26 00:30:51 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8C81016C9E4 for ; Fri, 26 May 2006 00:25:22 +0000 (UTC) (envelope-from mf.danger@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.187]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6807D43D46 for ; Fri, 26 May 2006 00:25:15 +0000 (GMT) (envelope-from mf.danger@gmail.com) Received: by nf-out-0910.google.com with SMTP id p46so50451nfa for ; Thu, 25 May 2006 17:25:14 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=ZsWn0F2n7TkL85xPOJNnkFLOdy6CZsGvsb8tSqWwJzODviR8tSf7HYbw4zqEh41BcGsOaP2tXzfE/zzb7TJj01+OFo4WTGVUt52Bx5QwbJbnEpgzJThr9AH54jIJcreukhRcyEM975us05RbNse34GuDKXUf2sSJPjSAbQI2dSE= Received: by 10.49.38.17 with SMTP id q17mr5702nfj; Thu, 25 May 2006 17:25:14 -0700 (PDT) Received: by 10.49.49.17 with HTTP; Thu, 25 May 2006 17:25:14 -0700 (PDT) Message-ID: <9f7850090605251725n5a37ff5fkd930a151e0a764c0@mail.gmail.com> Date: Thu, 25 May 2006 17:25:14 -0700 From: "marty fouts" To: "James Mansion" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <4475E99C.5000502@nortel.com> Cc: Alexander Leidinger , Poul-Henning Kamp , Andrew Atrens , small@freebsd.org, current@freebsd.org Subject: Re: FreeBSD's embedded agenda X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 May 2006 00:30:53 -0000 On 5/25/06, James Mansion wrote: > > Assume you have cron drive a flush once an hour and > consider how long until a sector dies, even if the drive > itself does no wear levelling at all (and I believe some > do it internally). I would be loathe to rely on a cron flush on a battery powered device.