From owner-freebsd-questions@FreeBSD.ORG Sun Oct 22 15:13:06 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 4A8AB16A47C for ; Sun, 22 Oct 2006 15:13:06 +0000 (UTC) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: from mail4.sea5.speakeasy.net (mail4.sea5.speakeasy.net [69.17.117.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 51C6743D46 for ; Sun, 22 Oct 2006 15:13:05 +0000 (GMT) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: (qmail 9933 invoked from network); 22 Oct 2006 15:13:05 -0000 Received: from dsl092-078-145.bos1.dsl.speakeasy.net (HELO be-well.ilk.org) ([66.92.78.145]) (envelope-sender ) by mail4.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 22 Oct 2006 15:13:04 -0000 Received: by be-well.ilk.org (Postfix, from userid 1147) id 638FC28432; Sun, 22 Oct 2006 11:13:04 -0400 (EDT) To: Matthew Pope References: <453B4ACD.1070802@teksavvy.com> From: Lowell Gilbert Date: Sun, 22 Oct 2006 11:13:04 -0400 In-Reply-To: <453B4ACD.1070802@teksavvy.com> (Matthew Pope's message of "Sun, 22 Oct 2006 06:41:17 -0400") Message-ID: <44k62ss7sv.fsf@be-well.ilk.org> User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: freebsd-questions@freebsd.org Subject: Re: problems after rebuild of 5.5 stable X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-questions@freebsd.org List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Oct 2006 15:13:06 -0000 Matthew Pope writes: [...] > for temp file for many of the prompts. Now my 5.5 kernel boots, but > there are a number of messages of the form: > source_rc_confs: not found > $ipnat_enable is not set properly - see rc.conf(5) > $ipfs_enable is not set properly - see rc.conf(5) > etc.... [...] > I later read in the mailing list that someone had a simliar problem > and solved it by re-running the mergemaster step. I tried that too, > and this time I selected answer to all the prompts about > conflicts. The default operation in mergemaster is to do nothing, so if you're going to choose the default the whole way, you might as well skip running mergemaster at all. Go back through mergemaster, and actually pay attention to the changes. On files you haven't modified, you will be able to (i)nstall the new versions of those files, but otherwise you will need to (m)erge them.