From owner-freebsd-bugs  Wed Aug 21 16:10:44 1996
Return-Path: owner-bugs
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id QAA11119
          for bugs-outgoing; Wed, 21 Aug 1996 16:10:44 -0700 (PDT)
Received: from time.cdrom.com (time.cdrom.com [204.216.27.226])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA11111
          for <bugs@FreeBSD.org>; Wed, 21 Aug 1996 16:10:42 -0700 (PDT)
Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with ESMTP id QAA18521; Wed, 21 Aug 1996 16:10:12 -0700 (PDT)
To: Eduard Vopicka <Eduard.Vopicka@vse.cz>
cc: bugs@FreeBSD.org
Subject: Re: sysinstall problem - 960801-SNAP 
In-reply-to: Your message of "Wed, 21 Aug 1996 15:22:12 +0200."
             <199608211322.AA12250@vse.vse.cz> 
Date: Wed, 21 Aug 1996 16:10:12 -0700
Message-ID: <18519.840669012@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-bugs@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

> 	custom installation
> 	partition -> sd1 -> W	# create single partition here
> 	bootmgr -> standard 	# of course, none should be also OK for sd1
> 	label -> create sd1s1e and sd1s1f, each of them being about 1/2 of
> 				disk capacity
> 	Write the label - getting coredump due to signal 11

Yeah, I found this already last week.  I'm now working on making
sysinstall actually perform the "add a disk" function, though some
fairly significant internal changes are probably going to be necessary
to really make it work.

					Jordan