From owner-freebsd-stable Fri May 22 11:13:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA10462 for freebsd-stable-outgoing; Fri, 22 May 1998 11:13:38 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from misery.sdf.com (misery.sdf.com [204.244.213.32]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA10430; Fri, 22 May 1998 11:13:29 -0700 (PDT) (envelope-from tom@sdf.com) Received: from tom by misery.sdf.com with smtp (Exim 1.82 #3) id 0ycvpD-0005GX-00; Fri, 22 May 1998 10:41:47 -0700 Date: Fri, 22 May 1998 10:41:41 -0700 (PDT) From: Tom To: Simon Shapiro cc: freebsd-stable@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: RE: DPT install problem In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On Fri, 22 May 1998, Simon Shapiro wrote: > > On 21-May-98 Tom wrote: > > > > I'm trying to use the boot-dpt 2.2.6-RELEASE floppy to bootstrap a new > > DPT based system. However, sysinstall hangs after newfs'ing the > > filesystems. > > > > I'm using a 21GB array, with auto-defaults for the filesystems, so /usr > > is over 20GB in size. If I delete /usr and replace it with a 500MB > > filesystem, leaving the remaining space unallocated, sysinstall has no > > problem completing the newfs step. > > > > Anyone else had problems with sysinstall on a mid-sized array like > > this? > > Yup. Me :-) > But not on 3.0-current. I noticed that 2.2 does not like huge partitions, > but this is not consnstent. 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. > Simon Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message