From owner-freebsd-stable Fri May 22 12:31:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA27645 for freebsd-stable-outgoing; Fri, 22 May 1998 12:31:28 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA27579; Fri, 22 May 1998 12:31:18 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id TAA29158; Fri, 22 May 1998 19:31:16 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id VAA01841; Fri, 22 May 1998 21:31:12 +0200 (MET DST) Message-ID: <19980522213111.03467@follo.net> Date: Fri, 22 May 1998 21:31:11 +0200 From: Eivind Eklund To: Tom , Simon Shapiro Cc: freebsd-stable@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: DPT install problem References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: ; from Tom on Fri, May 22, 1998 at 10:41:41AM -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On Fri, May 22, 1998 at 10:41:41AM -0700, Tom wrote: > Yes, it seems to be a sysinstall interaction. If I leave the space > unallocated, and then disklabel and newfs it later, it works fine. > > Currently it is pretty hard to bootstrap a new DPT system. You have to > be able to build a kernel somewhere else as sysinstall will install a > non-DPT kernel, and you can't use sysinstall to allocate large DPT > partitions. I fear for the new user. sysinstall doesn't do this anymore. The DPT driver is activated as part of the standard sysinstall now. As for large arrays: I think that will have to be left to you that actually have those large arrays - it is kind of difficult for us others to find out where the problem is. I suspect libdisk might be the culprit; it interact with the slice code using different IOCTLs than disklabel, IIRC. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message