From owner-freebsd-questions Sun Apr 30 13:33:21 1995 Return-Path: questions-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA03401 for questions-outgoing; Sun, 30 Apr 1995 13:33:21 -0700 Received: from iworks.InterWorks.org (iworks.interworks.org [128.255.18.10]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id NAA03394 for ; Sun, 30 Apr 1995 13:33:16 -0700 Received: by iworks.InterWorks.org (1.37.109.8/16.2) id AA13164; Sun, 30 Apr 1995 15:30:36 -0500 Message-Id: <9504302030.AA13164@iworks.InterWorks.org> Date: Sun, 30 Apr 1995 15:30:36 -0500 From: "Daniel M. Eischen" To: freebsd-questions@FreeBSD.org Subject: Re: your mail Sender: questions-owner@FreeBSD.org Precedence: bulk >> I think this is an excellent idea... Jordan? What are the chances of >> Walnut Creek offering a FreeBSD-SNAP subscription? I'd happily pay >> for a monthly or semi-monthly CDROM. Say a couple hundred bucks a year? >We'd be happy to do it, if people REALLY thought there was a demand. > >Well? Well, if there was an easy way to upgrade from snap to snap without overwriting any files that you have changed for a particular setup... Please correct me if there is an easier way than to log and save the changed files, or writing scripts that will install the new snap but check the dates on the files since the last snap and prompt for verification. I guess I want a kind of interactive sup, that can accept as input the date of the last snap (or any date), then update the files that haven't changed and prompt for those that have. This would be of help even for people with out the FreeBSD SNAP subscription. Dan Eischen deischen@iworks.InterWorks.org