From owner-freebsd-hackers  Fri Dec 27 15:19:54 1996
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.4/8.8.4) id PAA13278
          for hackers-outgoing; Fri, 27 Dec 1996 15:19:54 -0800 (PST)
Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211])
          by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id PAA13273
          for <freebsd-hackers@freebsd.org>; Fri, 27 Dec 1996 15:19:51 -0800 (PST)
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id QAA25462; Fri, 27 Dec 1996 16:13:05 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199612272313.QAA25462@phaeton.artisoft.com>
Subject: Re: mount -o noatime unsupported in -current?
To: joerg_wunsch@uriah.heep.sax.de
Date: Fri, 27 Dec 1996 16:13:05 -0700 (MST)
Cc: freebsd-hackers@freebsd.org
In-Reply-To: <199612242118.WAA13246@uriah.heep.sax.de> from "J Wunsch" at Dec 24, 96 10:18:03 pm
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> > Yes, this is a nice trick ;) Then rm -rf works like hell ;-))
> > It's blindly fast and very dangerous ;)
> 
> It's not that risky.  In particular, if all you're doing is a large
> `rm' operation, fsck should always be able to repair the filesystem
> even in case of a catastrophic failure.

This is true, as long as you do *nothing* other than the large rm
before remounting sync...


					Terry Lambert
					terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.