Date: Sat, 29 Aug 1998 01:45:00 -0500 From: "Matthew D. Fuller" <fullermd@futuresouth.com> To: "Jordan K. Hubbard" <jkh@time.cdrom.com> Cc: Mike Smith <mike@smith.net.au>, committers@FreeBSD.ORG Subject: Re: make.conf Message-ID: <19980829014500.39906@futuresouth.com> In-Reply-To: <23567.904356631@time.cdrom.com>; from Jordan K. Hubbard on Fri, Aug 28, 1998 at 07:10:31PM -0700 References: <199808281849.SAA06317@dingo.cdrom.com> <23567.904356631@time.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Aug 28, 1998 at 07:10:31PM -0700, Jordan K. Hubbard woke me up to tell me: > > For rc.conf and make.conf, which contains only variable declarations, > this is actually pretty easy since you really just have to: I've been mulling and ruminating, and occasionally thinking about something like this. What I was looking at (which is only forward-looking, hackish for backwards) is something along the lines of: 1) on install, copy pristine rc.conf to, say, /var/backups 2) on upgrade, do a diff between that and exiting /etc/rc.conf, to see local mods 3) perform magical incantation copying over new rc.conf, and reintegrating changed lines. Have a -i switch to see and OK the additions (read: re-merges) to the (new) rc.conf, have it log diffs between the old backup rc.conf and the new pristine rc.conf, etc. Now, that doesn't handle the existing systems of course. But for new...? Who wants to flame me about it first? *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* | FreeBSD; the way computers were meant to be | * "The only reason I'm burning my candle at both ends, is * | that I haven't figured out how to light the middle yet."| * fullermd@futuresouth.com :-} MAtthew Fuller * | http://keystone.westminster.edu/~fullermd | *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19980829014500.39906>