From owner-freebsd-hackers Fri Jul 21 21:49:43 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id VAA09453 for hackers-outgoing; Fri, 21 Jul 1995 21:49:43 -0700 Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.cdrom.com (8.6.11/8.6.6) with ESMTP id VAA09447 ; Fri, 21 Jul 1995 21:49:40 -0700 Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.11/8.6.9) with SMTP id VAA26497; Fri, 21 Jul 1995 21:48:56 -0700 To: Imperial Irrigation District cc: freebsd-hackers@freefall.cdrom.com, hsu@cs.hut.fi, jmacd@freefall.cdrom.com, karl@mcs.com, terry@cs.weber.edu Subject: Re: What people are doing with FBSD In-reply-to: Your message of "Fri, 21 Jul 1995 21:54:27 PDT." <199507220454.VAA11103@lightlink.satcom.net> Date: Fri, 21 Jul 1995 21:48:55 -0700 Message-ID: <26495.806388535@time.cdrom.com> From: "Jordan K. Hubbard" Sender: hackers-owner@FreeBSD.org Precedence: bulk Yes, we already have work underway for this - it's called /etc/sysconfig, at least in part. Jordan > What suggestion? Provide an upgrade path? Trust me, we're working > on it! :-) > > Sorry, I didn't make myself clear. > The suggestions refer to (1) seperate the configuration data > from the executable scripts such as rc, rc.local, netstart, ...etc. > The advantage of seperating the configuration data from the executable script s > is easier to debug for both the user and the developer. > (2) provide an upgrade path. That would speed up the development too because > the current developer can upgrade to the latest and greatest. Moreover, that > would close the gap between commercial grade OS and non-commercial OS. > Most importantly provide an upgrade path is user friendly. Make the user > happy. >