From owner-freebsd-current@FreeBSD.ORG Mon May 23 04:37:00 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E26DB16A41C for ; Mon, 23 May 2005 04:37:00 +0000 (GMT) (envelope-from david.freebsd@verizon.net) Received: from vms042pub.verizon.net (vms042pub.verizon.net [206.46.252.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id AF8FF43D48 for ; Mon, 23 May 2005 04:37:00 +0000 (GMT) (envelope-from david.freebsd@verizon.net) Received: from OSTest ([68.161.118.114]) by vms042.mailsrvcs.net (Sun Java System Messaging Server 6.2 HotFix 0.04 (built Dec 24 2004)) with ESMTPA id <0IGX006G9E5NQT19@vms042.mailsrvcs.net> for freebsd-current@freebsd.org; Sun, 22 May 2005 23:36:59 -0500 (CDT) Date: Sun, 22 May 2005 23:40:27 -0400 From: David Gurvich In-reply-to: <20050522114524.B27009@carver.gumbysoft.com> To: freebsd-current@freebsd.org Message-id: <200505222340.27785.david.freebsd@verizon.net> MIME-version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7bit Content-disposition: inline References: <20050518051111.GA33262@Athena.infor.org> <200505210727.23320.david.freebsd@verizon.net> <20050522114524.B27009@carver.gumbysoft.com> User-Agent: KMail/1.8 Subject: Re: Newest loader from CVS not working X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 May 2005 04:37:01 -0000 On Sunday 22 May 2005 14:45, Doug White wrote: > On Sat, 21 May 2005, David Gurvich wrote: > > New cvsup cycle has not fixed the problem. Might it have anything to do > > with the fact my freebsd partition is not the first partition? > > Unlikely ... are you _sure_ you updated your sources correctly and you're > booting the fixed loader? I am sure. I had previously copied the old loader to a backup location and then copied that to /boot/loader. Then the cvsup, buildworld kernel and install cycle. The new loader does what all the previous loaders did that failed to work correctly. It would get to a point where I could either escape to the #boot prompt and have it use the older loader or go into a reboot cycle. I am currently using the older loader. Using the older loader I have had no problems with the system other than KWrite crashing when doing a search.