From owner-freebsd-hackers  Thu Sep  5 23:47:42 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id XAA00716
          for hackers-outgoing; Thu, 5 Sep 1996 23:47:42 -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 XAA00707
          for <hackers@freebsd.org>; Thu, 5 Sep 1996 23:47:38 -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 XAA15663; Thu, 5 Sep 1996 23:47:15 -0700 (PDT)
To: Philippe Regnauld <regnauld@tetard.glou.eu.org>
cc: bde@zeta.org.au (Bruce Evans), hackers@freebsd.org (hackers)
Subject: Re: reported disk corruption 
In-reply-to: Your message of "Thu, 05 Sep 1996 21:43:14 +0200."
             <199609051943.VAA01481@tetard.glou.eu.org> 
Date: Thu, 05 Sep 1996 23:47:14 -0700
Message-ID: <15661.841992434@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> 	I then (W)rite it out, and switch to the partition ed.  There I 
> 	mount the existing partitions, and add the new part., which I decide
> 	to mount as spare.  
> 
> 	I write out the changes, and *WHAM*, sysinstall dumps core.

I know, and I know why it's happening (it's actually probably not what
you think).  In setting out to fix it, however, I needed to started
modularizing certain parts of sysinstall which are poorly modularized
and, after going about 2 days into that work, I realized that I was
effectively duplicating the work I already had going in parallel with
"setup", so I canned the sysinstall hacking and went back to setup
with a greater committment to getting it to BETA status, where one
could actually install a system with it.  I'll make no predictions,
but I can say that it's my #1 project at the moment.

					Jordan