From owner-freebsd-questions@FreeBSD.ORG Fri Apr 7 17:53:17 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 0BCCE16A402 for ; Fri, 7 Apr 2006 17:53:17 +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 634EC43D75 for ; Fri, 7 Apr 2006 17:53:08 +0000 (GMT) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: (qmail 1170 invoked from network); 7 Apr 2006 17:53:08 -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 ; 7 Apr 2006 17:53:08 -0000 Received: by be-well.ilk.org (Postfix, from userid 1147) id AFB9828423; Fri, 7 Apr 2006 13:53:07 -0400 (EDT) Sender: lowell@be-well.ilk.org To: Garrett Cooper References: <820FAFD6-ED04-41BE-A0C6-209980A7B376@u.washington.edu> <20060407080957.351b13b0.wmoran@collaborativefusion.com> <4436A3C4.5020505@u.washington.edu> From: Lowell Gilbert Date: 07 Apr 2006 13:53:07 -0400 In-Reply-To: <4436A3C4.5020505@u.washington.edu> Message-ID: <44acaxp918.fsf@be-well.ilk.org> Lines: 9 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: freebsd-questions@freebsd.org Subject: Re: Login broken and rc.conf variables suddenly invalid after kernel/world upgrade (?!?!) 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: Fri, 07 Apr 2006 17:53:17 -0000 Garrett Cooper writes: > By the way, I also ran mergemaster as shown above. I forgot to > originally include that. Did you also forget to mention building and installing the new kernel before the reboot? If you actually left that step out, it would explain much of your trouble.