From owner-freebsd-arch Tue Sep 12 17: 4:47 2000 Delivered-To: freebsd-arch@freebsd.org Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229]) by hub.freebsd.org (Postfix) with ESMTP id 6DEE437B43C for ; Tue, 12 Sep 2000 17:04:45 -0700 (PDT) Received: from winston.osd.bsdi.com (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e8D04bU85918; Tue, 12 Sep 2000 17:04:38 -0700 (PDT) (envelope-from jkh@winston.osd.bsdi.com) To: Shaun Jurrens Cc: arch@FreeBSD.ORG Subject: Re: sysinstall specification (was: build tools as...) In-Reply-To: Message from Shaun Jurrens of "Fri, 01 Sep 2000 02:40:57 +0200." <20000901024057.B3659@dakota.priv.shamz.net> Date: Tue, 12 Sep 2000 17:04:37 -0700 Message-ID: <85914.968803477@winston.osd.bsdi.com> From: Jordan Hubbard Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > A generally recognized method of solving complex problems is to > subdivide them into manageable parts. Modularity in programming, > design, and problem solving have enough aspects in common, that this > little treatise might help. My suggestion is simply that those > "fathers" of the current sysinstaller make the design of a new > sysinstaller simpler to those not possessing the years of experience > with the pitfalls of the gradual "monster" now known as sysinstall A good suggestion, and one I've just taken to heart in a 5000+ word document I just posted to hackers@freebsd.org and cc'd to committers@freebsd.org. If others would like to see it here and/or would like a personal copy, just let me know - I'm loath to post such a large document to too many places and arch has always had a somewhat limited readership. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message