From owner-freebsd-stable Thu Apr 16 12:10:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA13044 for freebsd-stable-outgoing; Thu, 16 Apr 1998 12:10:19 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from hub.org (hub.org [209.47.148.200]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA13016 for ; Thu, 16 Apr 1998 19:10:08 GMT (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by hub.org (8.8.8/8.7.5) with SMTP id PAA03437; Thu, 16 Apr 1998 15:10:06 -0400 (EDT) Date: Thu, 16 Apr 1998 15:10:05 -0400 (EDT) From: The Hermit Hacker To: Wes Peters - Softweyr LLC cc: lrios , stable@FreeBSD.ORG Subject: Re: Linux And FreeBSD In-Reply-To: <199804161904.NAA25961@xmission.xmission.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On Thu, 16 Apr 1998, Wes Peters - Softweyr LLC wrote: > Mount your mail spool async and you'll makeup the difference. > The linux filesystem does this by default. Not a great idea > in the face of system crashes; async mounts tend to leave the > disk scrambled beyond repair, but if Linux does it for you, > FreeBSD with async is no worse. Not completely accurate...I've had a bugger of a time with my -stable box and crashes, yet my ASYNC mounted drives have *yet* to cause me any grief. I don't do it on anything i consider to be critical, so just use it for news, but my history file is mounted async, and I imagine I would notice corruption very quickly in that... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message