From owner-freebsd-current  Thu Jul 23 21:05:34 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id VAA05610
          for freebsd-current-outgoing; Thu, 23 Jul 1998 21:05:34 -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 VAA05598
          for <current@FreeBSD.ORG>; Thu, 23 Jul 1998 21:05:27 -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 VAA02204;
	Thu, 23 Jul 1998 21:04:09 -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 19:04:48 PDT."
             <Pine.BSF.3.96.980723190320.27155A-100000@shell.uniserve.ca> 
Date: Thu, 23 Jul 1998 21:04:09 -0700
Message-ID: <2200.901253049@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>   Yes, but sysinstall bugs will probably force you to do most of the
> filesystem setup manually.  See archives.  

Please don't spread FUD.  The "sysinstall bugs" have already been
documented, announced and fixed, nor did they have anything to do with
this issue.

- Jordan

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