From owner-freebsd-current@FreeBSD.ORG Thu Apr 2 07:40:26 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 9541B106566B for ; Thu, 2 Apr 2009 07:40:26 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id B46318FC19 for ; Thu, 2 Apr 2009 07:40:25 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from porto.topspin.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id KAA04378; Thu, 02 Apr 2009 10:39:54 +0300 (EEST) (envelope-from avg@icyb.net.ua) Received: from localhost.topspin.kiev.ua ([127.0.0.1] helo=edge.pp.kiev.ua) by porto.topspin.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1LpHWk-0005At-B0; Thu, 02 Apr 2009 10:39:54 +0300 Message-ID: <49D46BC7.5030307@icyb.net.ua> Date: Thu, 02 Apr 2009 10:39:51 +0300 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.19 (X11/20090114) MIME-Version: 1.0 To: User Wblock References: <4451ccf20903300123p4df9c1d7k4c4138ad25d2d4af@mail.gmail.com> <49D0E44C.60103@phat.za.net> <49D1001E.2050405@icyb.net.ua> <49D1C3E6.3050207@icyb.net.ua> In-Reply-To: X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit 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 07:40:26 -0000 on 02/04/2009 03:27 User Wblock said the following: > 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. Thank you! >>> 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. Well, it is needed if you want to update your btx / boot2 code and not needed otherwise. The manual page can't know your intentions :) >>> 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)..." Yes, this will definitely be more accurate. OTOH, I think it was clear enough from the context of this thread (e.g. see subject line). >>> 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". http://svn.freebsd.org/viewvc/base/head/sys/boot/i386/btx/btx/ You can easily continue from here. >>> * 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? It can mean either. The people who did/do have the problem experienced it very consistently. As for telling - I know of no easy way. You can dd first 8k of your boot slice, hexdump it and then compare with hexdump of /boot/boot installed by installworld. >>> Or just those using certain partitioning features? >>> * There's no mention in /usr/src/UPDATING. Was it mentioned anywhere? BTW, I think it was not mentioned in UPDATING because only a very small minority of users was affected or at least reported the problem. -- Andriy Gapon