From owner-freebsd-questions@FreeBSD.ORG Thu Feb 9 14:31:38 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 4393C16A423 for ; Thu, 9 Feb 2006 14:31:38 +0000 (GMT) (envelope-from chuck.teal@yahoo.com) Received: from smtp107.plus.mail.mud.yahoo.com (smtp107.plus.mail.mud.yahoo.com [68.142.206.240]) by mx1.FreeBSD.org (Postfix) with SMTP id CB96943D45 for ; Thu, 9 Feb 2006 14:31:37 +0000 (GMT) (envelope-from chuck.teal@yahoo.com) Received: (qmail 63485 invoked from network); 9 Feb 2006 14:31:36 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Received:From:Organization:To:Subject:Date:User-Agent:References:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Content-Disposition:Message-Id; b=NIabvb4mMFfdW7wYaFH+7bkKNQ55Jra0PkJX6cmlTUxVtttcMWEs2VwxzFHZ1UF4pj9+f/KUFViLoFtAxritzAzmrMyRSlUoc+mKEiXhYMla5TZpLG3yUw9DOjMmYyP1wv7u8cwfiWTGad8rxID6vx8N8Jjzw3EHFtBqyksbTBE= ; Received: from unknown (HELO dhcp111175.physics.fsu.edu) (silverback011@128.186.111.175 with plain) by smtp107.plus.mail.mud.yahoo.com with SMTP; 9 Feb 2006 14:31:36 -0000 From: Chuck Teal Organization: Personal To: freebsd-questions@freebsd.org Date: Thu, 9 Feb 2006 09:31:06 -0500 User-Agent: KMail/1.8.2 References: <20060208201350.46ACE16A456@hub.freebsd.org> <20060209011433.GA19079@ns.museum.rain.com> In-Reply-To: <20060209011433.GA19079@ns.museum.rain.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200602090931.06541.chuck.teal@yahoo.com> 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 14:31:38 -0000 On Wednesday February 8 2006 20:14, James Long wrote: > > 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 I agree. It would be much safer this way. Thanks for pointing this out. Chuck