From owner-freebsd-current@freebsd.org Tue May 10 14:31:11 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0B460B35CBC for ; Tue, 10 May 2016 14:31:11 +0000 (UTC) (envelope-from allanjude@freebsd.org) Received: from mx1.scaleengine.net (mx1.scaleengine.net [209.51.186.6]) by mx1.freebsd.org (Postfix) with ESMTP id E3E3917D4 for ; Tue, 10 May 2016 14:31:10 +0000 (UTC) (envelope-from allanjude@freebsd.org) Received: from [10.1.1.2] (unknown [10.1.1.2]) (Authenticated sender: allanjude.freebsd@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id 6A6ACD92B for ; Tue, 10 May 2016 14:31:04 +0000 (UTC) Subject: Re: HEADS-UP: installworld on r299292 through r299317 will replace master.passwd, passwd, and group files To: freebsd-current@freebsd.org References: <20160510055341.GA47527@FreeBSD.org> <20160510081844.54f1cb28@freyja.zeit4.iv.bundesimmobilien.de> <20160510063229.GC47527@FreeBSD.org> From: Allan Jude Message-ID: <5731F0A7.1060403@freebsd.org> Date: Tue, 10 May 2016 10:31:03 -0400 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2 MIME-Version: 1.0 In-Reply-To: <20160510063229.GC47527@FreeBSD.org> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 May 2016 14:31:11 -0000 On 2016-05-10 02:32, Glen Barber wrote: > On Tue, May 10, 2016 at 08:25:22AM +0200, Thomas Zander wrote: >> On 10 May 2016 at 08:18, O. Hartmann wrote: >> >>> I haven't figured out so far how far this goes. Lucky for those having >>> recent /etc/ backups. A pity FreeBSD doens't backup this by default. >> >> After having shot myself in the foot some time ago, "zfs snapshot" has >> become a part of my standard upgrade procedures :-) >> > > No argument that this is valuable, but we cannot rely on filesystem > specific solutions. Similar topic came up a few days ago following > lunch. It got me thinking of a better way to ensure this kind of thing > does not require home-grown foot protection from cannons. > > It should be fairly trivial to automatically backup /etc (and related) > when 'distribution' is run, either intentionally or accidentally (or by > commit mistakes, such as this). > > Glen > I wonder if you couldn't actually package it. Before installing the new /etc, it would create a package of what is in your old /etc and put it somewhere safe, so an upgrade could be reverted by manually installing that package. -- Allan Jude