From owner-freebsd-current Tue Oct 6 07:23:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA24175 for freebsd-current-outgoing; Tue, 6 Oct 1998 07:23:54 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from trinity.radio-do.de (trinity.Radio-do.de [193.101.164.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA24168 for ; Tue, 6 Oct 1998 07:23:51 -0700 (PDT) (envelope-from fn@trinity.radio-do.de) Received: (from fn@localhost) by trinity.radio-do.de (8.9.1/8.8.5/RADIO-1.1) id QAA06141; Tue, 6 Oct 1998 16:23:22 +0200 (CEST) Message-ID: <19981006162322.A6132@radio-do.de> Date: Tue, 6 Oct 1998 16:23:22 +0200 From: Frank Nobis To: Karl Pielorz , current@FreeBSD.ORG Subject: Re: Toasting /etc/rc.conf... References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from Karl Pielorz on Tue, Oct 06, 1998 at 01:26:24PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Oct 06, 1998 at 01:26:24PM +0100, Karl Pielorz wrote: > This is probably a very minor point in the grand scheme of things, but I > managed to complete delete my /etc/rc.conf the other day by: Staying current means, you have always the chance to nuke your system. I have two strategies to take this into account. 1.) Backup everything you need to external media, which you can access with a boot&fiyxit floppy. This is a MO drive in my case. One should test a boot&fixit floppy before the mess happens. 2.) To make upgrading /etc/rc.conf simple, don't edit in rc.conf but in rc.conf.local instead. Regards Frank To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message