From owner-freebsd-config Wed Jan 22 04:58:39 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id EAA03228 for config-outgoing; Wed, 22 Jan 1997 04:58:39 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA03219; Wed, 22 Jan 1997 04:58:36 -0800 (PST) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.8.4/8.6.9) with ESMTP id EAA22825; Wed, 22 Jan 1997 04:57:34 -0800 (PST) To: Michael Smith cc: davidn@unique.usn.blaze.net.au, hosokawa@mt.cs.keio.ac.jp, keithl@wakko.gil.net, chat@freebsd.org, config@freebsd.org Subject: Re: Kernel configuration In-reply-to: Your message of "Wed, 22 Jan 1997 18:02:02 +1030." <199701220732.SAA14304@genesis.atrad.adelaide.edu.au> Date: Wed, 22 Jan 1997 04:57:34 -0800 Message-ID: <22821.853937854@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-config@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I should also perhaps have observed that the software I'm talking > about here is a client-server configuration utility, with the client > deriving all of the metaconfiguration data from the server at session > startup, and generating the UI on the fly based on this data. > > So I guess you could say I've been down this road before, but at the > same time to date I've been walking it alone, and new perspectives > are proving very enlightening. 8) Actually, where's your code for this lately? I was just thinking about this the other day and wanted to play with the concept a little. :-) Jordan