From owner-freebsd-hackers  Fri Jul 21 09:49:10 1995
Return-Path: hackers-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.11/8.6.6) id JAA10295
          for hackers-outgoing; Fri, 21 Jul 1995 09:49:10 -0700
Received: from cs.weber.edu (cs.weber.edu [137.190.16.16])
          by freefall.cdrom.com (8.6.11/8.6.6) with SMTP id JAA10287
          ; Fri, 21 Jul 1995 09:49:07 -0700
Received: by cs.weber.edu (4.1/SMI-4.1.1)
	id AA06025; Fri, 21 Jul 95 10:41:37 MDT
From: terry@cs.weber.edu (Terry Lambert)
Message-Id: <9507211641.AA06025@cs.weber.edu>
Subject: Re: What people are doing with FBSD
To: iidpwr@lightlink.satcom.net (Imperial Irrigation District)
Date: Fri, 21 Jul 95 10:41:37 MDT
Cc: jkh@time.cdrom.com, karl@mcs.com, freebsd-hackers@freefall.cdrom.com,
        hsu@cs.hut.fi, jmacd@freefall.cdrom.com
In-Reply-To: <199507210057.RAA03950@lightlink.satcom.net> from "Imperial Irrigation District" at Jul 20, 95 05:57:43 pm
X-Mailer: ELM [version 2.4dev PL52]
Sender: hackers-owner@FreeBSD.org
Precedence: bulk

> Yes. I am interested. I would like to see sysinstall can fdisk and disklabel
> the second hard disk. Or to upgrade the old version to a newer version w/o
> reinstalling the whole new system. It is a big problem with me to upgrade
> since I have to resinstalling the whole new system.

The "upgrade problem" can't go away until the system configuration
data has been divorced for the configuration implementation.

As long as there is one shell script that must be modified to
reflect configuration information, upgrading will be a bitch.

It's only when new developement doesn't affect the files containing
configuration data that upgrades will become easy.


					Terry Lambert
					terry@cs.weber.edu
---
Any opinions in this posting are my own and not those of my present
or previous employers.