From owner-freebsd-current@FreeBSD.ORG Mon Apr 15 19:58:32 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 825A478F for ; Mon, 15 Apr 2013 19:58:32 +0000 (UTC) (envelope-from george+freebsd@m5p.com) Received: from mailhost.m5p.com (ip-2-1-0-2.r03.asbnva02.us.ce.gin.ntt.net [IPv6:2001:418:0:5000::16]) by mx1.freebsd.org (Postfix) with ESMTP id 3EB0E172E for ; Mon, 15 Apr 2013 19:58:32 +0000 (UTC) Received: from wonderland.m5p.com (localhost [IPv6:::1]) by mailhost.m5p.com (8.14.5/8.14.5) with ESMTP id r3FJwQn5009704 for ; Mon, 15 Apr 2013 15:58:31 -0400 (EDT) (envelope-from george+freebsd@m5p.com) Message-ID: <516C5BE2.50005@m5p.com> Date: Mon, 15 Apr 2013 15:58:26 -0400 From: George Mitchell User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:15.0) Gecko/20121125 Thunderbird/15.0.1 MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: After a source upgrade from 8.3-RELEASE to r249432 (HEAD) Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.73 on 10.100.0.3 X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.7 (mailhost.m5p.com [IPv6:::1]); Mon, 15 Apr 2013 15:58:31 -0400 (EDT) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 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, 15 Apr 2013 19:58:32 -0000 It was pretty successful. All my 8.3 packages are still running very happily, though at some point I imagine I will have to update and recompile them. But ... When I press ENTER in the boot0 screen, I get the hyphen that will start spinning after a timeout and begin loading boot1 (which, as far as I know, I have not updated). boot1 (I think) presents me with a prompt that does not respond to key presses on the keyboard. It times out and continues loading anyway. At this stage, I am always presented with a manual mountroot: prompt, and I have to type "ufs:/dev/ada0s1a" to get any further. Does this just mean I should update the boot code? Presumably "fdisk -B" won't change anything. Should I just do "bsdlabel -B"? (It's an MBR disk.) Aside from this glitch, I'm very happy with how smoothly the update went. And I wouldn't be complaining, except that I'm tired of having to type "ufs:/dev/ada0s1a" every time I boot. -- George Mitchell