From owner-freebsd-current Mon Dec 13 23:18:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id A7D761520C for ; Mon, 13 Dec 1999 23:18:39 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id XAA02181; Mon, 13 Dec 1999 23:19:05 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Eric Jones Cc: current@FreeBSD.ORG Subject: Re: sysinstall: is it really at the end of its lifecycle? In-reply-to: Your message of "Mon, 13 Dec 1999 22:42:51 EST." <3855BCBB.578EA6A1@colltech.com> Date: Mon, 13 Dec 1999 23:19:05 -0800 Message-ID: <2177.945155945@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > that "This product is currently at the end of its life cycle and will > eventually > be replaced." The handy thing about "eventually" is that it can be a long time. :) > Amusingly, the man page author (Jordan?) says, "This utility is a > prototype which lasted approximately 3 years past its expiration > date and is greatly in need of death." All true, I'm afraid. All I can say is that efforts to revive the effort to replace sysinstall are underway and we're even trying to throw some money-shaped darts at the problem in hopes that we'll hit something. I'm cautiously pessimistic, so we'll see. :) In any case, nothing I'm currently trying to bootstrap here will see the light of day before 5.0 at this point, so hacking sysinstall is probably not such a bad prospect for the 3.x and 4.x releases to come. I've even (*shudder*) been putting some work into cleaning the code up a bit these past couple of days. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message