From owner-freebsd-hackers Thu Aug 21 15:21:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA23191 for hackers-outgoing; Thu, 21 Aug 1997 15:21:32 -0700 (PDT) Received: from zippy.dyn.ml.org (garbanzo@libya-197.ppp.hooked.net [206.169.227.197]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA23184 for ; Thu, 21 Aug 1997 15:21:26 -0700 (PDT) Received: from localhost (garbanzo@localhost) by zippy.dyn.ml.org (8.8.7/8.8.7) with SMTP id PAA01462; Thu, 21 Aug 1997 15:22:04 -0700 (PDT) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Thu, 21 Aug 1997 15:22:04 -0700 (PDT) From: Alex X-Sender: garbanzo@zippy.dyn.ml.org To: Randall Hopper cc: hackers@FreeBSD.ORG Subject: Re: ? "sysinstall" errors labeling a new disk In-Reply-To: <19970821105527.53931@ct.picker.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 21 Aug 1997, Randall Hopper wrote: > Shouldn't sysinstall be doing a disklabel? Any idea what I'm doing wrong > or if this is a sysinstall bug? > > I'd welcome any tips, suggestions, and even enlightening flames. Before I > resort to disklabeling via cmd-line, I'd like to make sure that sysinstall > isn't an option -- it's definitely the easier and safer way to go if it can > work for folks that don't Yup, that's a bug alright. There was a similar bug that would make sysinstall error out if you tried to label a disk slice, which was fixed a few days ago in the -current sources. Your best bet though is probably to download a 2.2 boot disk and load sysinstall from there, or try cvsup'n the sources and making /usr/src/release/sysinstall. - alex