From owner-freebsd-current Thu Jul 23 21:26:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA09360 for freebsd-current-outgoing; Thu, 23 Jul 1998 21:26:32 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id VAA09350 for ; Thu, 23 Jul 1998 21:26:28 -0700 (PDT) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 0yzZQZ-0000pE-00; Thu, 23 Jul 1998 21:25:55 -0700 Date: Thu, 23 Jul 1998 21:25:52 -0700 (PDT) From: Tom X-Sender: tom@shell.uniserve.ca To: "Jordan K. Hubbard" cc: Doug White , Lee Reese , current@FreeBSD.ORG Subject: Re: Viability of -current for Usenet News In-Reply-To: <2230.901253142@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 23 Jul 1998, Jordan K. Hubbard wrote: > > 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. Strange. I've never had a FreeBSD install onto a DPT system work properly. I was also under the impression that you did not have a DPT card to test with, nor enough hard drives to create a mid-sized array. > - Jordan Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message