Date: Wed, 16 Sep 1998 01:33:12 -0700 (PDT) From: ben@ben.com To: freebsd-gnats-submit@FreeBSD.ORG Subject: misc/7945: 2.2.6->2.2.7 upgrade clobbered /etc without backing it up Message-ID: <199809160833.BAA01873@hub.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 7945 >Category: misc >Synopsis: 2.2.6->2.2.7 upgrade clobbered /etc without backing it up >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Wed Sep 16 01:40:01 PDT 1998 >Last-Modified: >Originator: Ben Jackson >Organization: >Release: 2.2.7 (now!) >Environment: FreeBSD pulsar.ben.com 2.2.7-RELEASE FreeBSD 2.2.7-RELEASE #0: Sun Sep 13 04:49:04 PDT 1998 bj@pulsar.ben.com:/usr/src/sys/compile/PULSAR i386 >Description: I used the Walnut Creek cdrom to to an upgrade from 2.2.6 (sysinstall "Upgrade" option). It prompted me for a directory to backup my etc dir (I gave it `/etc.bak') and rattled the disk while claiming to be doing that. It said the NEW etc files would be in an `upgrade' directory. Towards the end it claimed I had no fstab, passwd or group files. In the end, all of my etc files were overwritten by the dist, I have no `upgrade' directory and NO ETC.BAK! I guess the scary warning should have scared me off, though I have managed to do deltas in the past... >How-To-Repeat: >Fix: I'm wondering if `/etc.bak' put it in the MFS rather than in /mnt, but of course you can't tell from the holographic shell... I suppose I got `upgrade' dir because the files were extracted directly into etc (a bug, but it explains my results). The workaround is to go get your offsite backup and restore /etc... >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199809160833.BAA01873>