From owner-freebsd-current@FreeBSD.ORG Thu Apr 2 00:27:13 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 644A8106566B for ; Thu, 2 Apr 2009 00:27:13 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id ED0B58FC15 for ; Thu, 2 Apr 2009 00:27:12 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.3/8.14.3) with ESMTP id n320RCkE036431; Wed, 1 Apr 2009 18:27:12 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.3/8.14.3/Submit) with ESMTP id n320RB2m036428; Wed, 1 Apr 2009 18:27:11 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Wed, 1 Apr 2009 18:27:11 -0600 (MDT) From: User Wblock To: Andriy Gapon In-Reply-To: <49D1C3E6.3050207@icyb.net.ua> Message-ID: References: <4451ccf20903300123p4df9c1d7k4c4138ad25d2d4af@mail.gmail.com> <49D0E44C.60103@phat.za.net> <49D1001E.2050405@icyb.net.ua> <49D1C3E6.3050207@icyb.net.ua> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.0.1 (wonkity.com [127.0.0.1]); Wed, 01 Apr 2009 18:27:12 -0600 (MDT) Cc: Aragon Gouveia , ccuiyyan@gmail.com, freebsd-current@freebsd.org Subject: Re: loader prompt doesn't work 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: Thu, 02 Apr 2009 00:27:13 -0000 On Tue, 31 Mar 2009, Andriy Gapon wrote: > on 31/03/2009 03:50 User Wblock said the following: >> On Mon, 30 Mar 2009, Andriy Gapon wrote: >>> There was a significant fix to boot code made recently by jhb. It is >>> now in head, stable/7 and stable/6. So you need to update to the >>> recent resources. What you also need (and what was not emphasized >>> enough, IMO) is to actually install new boot code (/boot/boot) to >>> your active slices after installworld completes. >>> >>> E.g.: >>> $ gpart bootcode -b /boot/boot adXsY >> >> The gpart manpage just makes me more confused about this. > > Your reply is quite confusing too - you put many different things into > the same heap. Okay, I'll try again. >> I don't know >> what a "protective" MBR is, or if I've got one. > > If you think that you have to know, then google is your friend. The question is "How can I tell if 'gpart bootcode -b /boot/boot adXsY'? is needed? The gpart man page is apparently not the place to start. >> Can you expand on this a little? > > On "this" what? On your statement above: >>> What you also need (and what was not emphasized enough, IMO) is to >>> actually install new boot code (/boot/boot) to your active slices >>> after installworld completes. Would it be more accurate if that sentence read: "What you also need *if you experience problems with the boot loader prompt* (and what was not emphasized enough, IMO)..." >> For instance: >> >> * When did it happen? > > "it" what? >>> There was a significant fix to boot code made recently by jhb. Hoping for something more specific than "recently". >> * Who needs to do this--everyone who has updated to a recent -CURRENT or >> -STABLE? > > If you don't have the problems described earlier in this thread than you > don't have to do anything. Does not having the problem mean the latest boot code is in place, or just that the particular system hasn't triggered the problem? Is there a way to tell if the installed boot code is up to date? >> Or just those using certain partitioning features? >> * There's no mention in /usr/src/UPDATING. Was it mentioned anywhere? -Warren Block * Rapid City, South Dakota USA