From owner-freebsd-current@FreeBSD.ORG Thu Dec 2 00:29:40 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9E50516A4CE; Thu, 2 Dec 2004 00:29:40 +0000 (GMT) Received: from ns1.xcllnt.net (209-128-86-226.bayarea.net [209.128.86.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id 18E0843D53; Thu, 2 Dec 2004 00:29:40 +0000 (GMT) (envelope-from marcel@xcllnt.net) Received: from ns1.xcllnt.net (localhost [127.0.0.1]) by ns1.xcllnt.net (8.13.1/8.13.1) with ESMTP id iB20Tdb6003035; Wed, 1 Dec 2004 16:29:39 -0800 (PST) (envelope-from marcel@ns1.xcllnt.net) Received: (from marcel@localhost) by ns1.xcllnt.net (8.13.1/8.13.1/Submit) id iB20Td43003034; Wed, 1 Dec 2004 16:29:39 -0800 (PST) (envelope-from marcel) Date: Wed, 1 Dec 2004 16:29:39 -0800 From: Marcel Moolenaar To: Scott Long Message-ID: <20041202002939.GA2834@ns1.xcllnt.net> References: <41AE3F80.1000506@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41AE3F80.1000506@freebsd.org> User-Agent: Mutt/1.4.2.1i cc: hackers@freebsd.org cc: "current@freebsd.org" Subject: Re: My project wish-list for the next 12 months X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 00:29:40 -0000 On Wed, Dec 01, 2004 at 03:02:40PM -0700, Scott Long wrote: > > 1. Keyboard multiplexer. I actually fail to stop thinking about a complete syscons and pcvt replacement. You know, the one and only console implementation that makes all others obsolete. Big plans, little time, yada yada yada... > 2. New installer. It may actually be interesting to see if we can make an expert system for this. When I think about implementing an installer (alas I've been doing that), I'm not so much interested in how things are packaged, or how it looks but rather what needs to be done, when and how all these actions relate and interact with each other. This is especially tricky when actions are triggered by the current configuration of the machine onto which one tries to install. Knowing all the possible activities and their dependencies should help establish a control flow through the installation process in such a way that users get asked only those questions that are relevent and also when it matters. One puts a UI on top of this to get a nice looking installer. At least, that's how I look at it... -- Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net