From owner-freebsd-current  Wed Apr 19 23:08:09 1995
Return-Path: current-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id XAA19459
          for current-outgoing; Wed, 19 Apr 1995 23:08:09 -0700
Received: from localhost (localhost [127.0.0.1])
          by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id XAA19452
          ; Wed, 19 Apr 1995 23:08:07 -0700
X-Authentication-Warning: freefall.cdrom.com: Host localhost didn't use HELO protocol
To: "Russell L. Carter" <rcarter@geli.com>
cc: davidg@Root.COM, current@FreeBSD.org
Subject: Re: wcarchive down 
In-reply-to: Your message of "Wed, 19 Apr 95 22:18:59 PDT."
             <199504200518.WAA03907@geli.clusternet> 
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Wed, 19 Apr 1995 23:08:07 -0700
Message-ID: <19451.798358087@freefall.cdrom.com>
From: Gary Palmer (FreeBSD/ARM Team) <gpalmer@freefall.cdrom.com>
Sender: current-owner@FreeBSD.org
Precedence: bulk

In message <199504200518.WAA03907@geli.clusternet>, "Russell L. Carter" writes:
>This is a helluva commitment to FreeBSD, might be messy to begin with but
>will likely root out many of those hard to find bugs right quick, with long
>term benefits for the community. 

And in the meantime, every time wcarchive goes down, Walnut Creek's name
get's slightly muddier. We were origionally waiting for 2.1 to come out, and
be properly tested, etc, etc, before even thinking of touching wcarchive,
but it spamming it's /dev/*sd* entries well enough so that we can't even
re-mount the root filesystem read-write kinda forced our hands.

Yes, it'll force a lot of obscure bugs into the open, but debugging wcarchive
isn't easy as we don't normally have any console access...

Gary