From owner-freebsd-current@FreeBSD.ORG Tue Mar 31 07:19:34 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 CF57E106566B for ; Tue, 31 Mar 2009 07:19:34 +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 153A38FC0C for ; Tue, 31 Mar 2009 07:19:33 +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 KAA23143; Tue, 31 Mar 2009 10:19:04 +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 1LoYFU-000MHA-At; Tue, 31 Mar 2009 10:19:04 +0300 Message-ID: <49D1C3E6.3050207@icyb.net.ua> Date: Tue, 31 Mar 2009 10:19:02 +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> 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: Tue, 31 Mar 2009 07:19:35 -0000 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. > 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. > Can you expand on this a little? On "this" what? > For instance: > > * When did it happen? "it" what? > * 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. > Or just those using certain partitioning features? > * There's no mention in /usr/src/UPDATING. Was it mentioned anywhere? -- Andriy Gapon