From owner-freebsd-current  Thu Jul 23 21:06:55 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id VAA05914
          for freebsd-current-outgoing; Thu, 23 Jul 1998 21:06:55 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA05909
          for <current@FreeBSD.ORG>; Thu, 23 Jul 1998 21:06:53 -0700 (PDT)
          (envelope-from jkh@time.cdrom.com)
Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1])
	by time.cdrom.com (8.8.8/8.8.8) with ESMTP id VAA02233;
	Thu, 23 Jul 1998 21:05:42 -0700 (PDT)
	(envelope-from jkh@time.cdrom.com)
To: Tom <tom@uniserve.com>
cc: Doug White <dwhite@resnet.uoregon.edu>, Lee Reese <lee@gwinnett.com>,
        current@FreeBSD.ORG
Subject: Re: Viability of -current for Usenet News 
In-reply-to: Your message of "Thu, 23 Jul 1998 20:47:38 PDT."
             <Pine.BSF.3.96.980723204143.27155E-100000@shell.uniserve.ca> 
Date: Thu, 23 Jul 1998 21:05:42 -0700
Message-ID: <2230.901253142@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>   This has gone for almost a year.  Talked about in frebsd-scsi for
> sure, and probably freebsd-stable.  Basically what happens, is that
> sysinstall hangs just after newfs'ing the filesystems.  The work around is

Uh, this sure is news to me.  I've *never* seen such symptoms in any
of the multiple test systems here nor has anyone sent me a bug report
detailing any such behavior.

- Jordan

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message