From owner-freebsd-questions@FreeBSD.ORG Thu Feb 9 01:14:41 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3213116A420 for ; Thu, 9 Feb 2006 01:14:41 +0000 (GMT) (envelope-from james_mapson@umpquanet.com) Received: from ns.museum.rain.com (gw-ipinc.museum.rain.com [65.75.192.74]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9541043D48 for ; Thu, 9 Feb 2006 01:14:40 +0000 (GMT) (envelope-from james_mapson@umpquanet.com) Received: from ns.museum.rain.com (localhost [127.0.0.1]) by ns.museum.rain.com (8.13.4/8.13.4) with ESMTP id k191EXeN019209 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES256-SHA bits=256 verify=NO); Wed, 8 Feb 2006 17:14:33 -0800 (PST) (envelope-from james@umpquanet.com) Received: (from james@localhost) by ns.museum.rain.com (8.13.4/8.13.4/Submit) id k191EXsh019208; Wed, 8 Feb 2006 17:14:33 -0800 (PST) (envelope-from james) Date: Wed, 8 Feb 2006 17:14:33 -0800 From: James Long To: freebsd-questions@freebsd.org, zhang Message-ID: <20060209011433.GA19079@ns.museum.rain.com> References: <20060208201350.46ACE16A456@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060208201350.46ACE16A456@hub.freebsd.org> User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-101.2 required=5.0 tests=ALL_TRUSTED, MAILTO_TO_SPAM_ADDR,USER_IN_WHITELIST autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on ns.museum.rain.com Cc: Subject: Re: update problems X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Feb 2006 01:14:41 -0000 > Date: Wed, 8 Feb 2006 13:25:38 -0500 > From: Chuck Teal > Subject: Re: update problems > To: freebsd-questions@freebsd.org > Message-ID: <200602081325.39122.chuck.teal@yahoo.com> > Content-Type: text/plain; charset="iso-8859-1" > > On Wednesday February 8 2006 10:40, Iantcho Vassilev wrote: > > If you haven`t delete the megremaster store directory(usually /var/....) > > just rerun it. - mergemaster > > and ask all the quesions by hand > > > > But first i would suggest to find the problem > > > > On 2/8/06, zhang wrote: > > > I've just update to 6.1-PRERELEASE from 6.0. Before I mergemaster -cv , > > > the system could work well . But when I mergemaster , I don't check the > > > differents carefully and choose the " i " option directly most of the > > > time . Now , all the network programmes can't work , I can't ping > > > localhost/127.0.0.1 , I can't use " tcpdump " , the c/s kinds like > > > xserver also go bad ; when the system start , many warnings such as > > > "...see rc.conf(5)" after dmesg messages. > > > How can I deal with it ? > > > Thanks! > > I had a similar problem just yesterday. Running mergemaster again did not fix > the issue. > > In my situation I messed up the /etc/defaults/rc.conf. It gave me several > error messages on boot up similar to yours. I just copied the rc.conf from > the examples directory and replaced the rc.conf in /etc/defaults/rc.conf. > Then I did a: > > shutdown now > exit > > It was working okay when I left this morning. > > I am not sure if this is a good idea or not. I just know it seems to have > solved my problem. I would keep a backup of the original file somewhere in > case you need to revert back to the original. chuck.teal@yahoo.com's advice is too narrow, IMO. The best practice I know is to back up the entire /etc directory tree before running mergemaster: ... rm -rf /etc.old cp -RLp /etc /etc.old mergemaster -v ... Then, if something goes wrong in mergemaster, you can just restore the backup and re-run mergemaster. Jim