From owner-freebsd-stable  Wed Mar 26 13:41:37 1997
Return-Path: <owner-stable>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id NAA29491
          for stable-outgoing; Wed, 26 Mar 1997 13:41:37 -0800 (PST)
Received: from rover.village.org (rover.village.org [204.144.255.49])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id NAA29472
          for <stable@freebsd.org>; Wed, 26 Mar 1997 13:41:33 -0800 (PST)
Received: from rover.village.org [127.0.0.1] 
	by rover.village.org with esmtp (Exim 1.60 #1)
	id 0wA0Rj-0005q8-00; Wed, 26 Mar 1997 14:41:27 -0700
To: "Richard Wackerbarth" <rkw@dataplex.net>
Subject: Re: SUP 
Cc: stable@freebsd.org
In-reply-to: Your message of "26 Mar 1997 15:38:18 CST."
		<AF5EF36E-1DA1D@204.69.236.50> 
References: <AF5EF36E-1DA1D@204.69.236.50>  
Date: Wed, 26 Mar 1997 14:41:27 -0700
From: Warner Losh <imp@village.org>
Message-Id: <E0wA0Rj-0005q8-00@rover.village.org>
Sender: owner-stable@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

In message <AF5EF36E-1DA1D@204.69.236.50> "Richard Wackerbarth" writes:
: or twice a day.  As for rebuilding partially trashed trees, I would
: argue that it that is necessary other than on extremely rare
: occasions, the user is not practicing "safe hex" and should change
: their methodology.

Hmmm, I've only had to reconstruct trees when I ran out of disk space
due to a large number of items coming into the tree.  What could I
have done to prevent that?  That's really the only problem I've had
with CTM other than an occasional "oops" where things like eBones or
secure have gone out accidentally...

I'll see about setting up the CTM stuff on the OpenBSD machine that
needs it.  Should be relatively simple...

Warner