From owner-freebsd-stable@FreeBSD.ORG Wed Mar 18 17:43:50 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ECF591065674; Wed, 18 Mar 2009 17:43:50 +0000 (UTC) (envelope-from stef-list@memberwebs.com) Received: from mx.npubs.com (mail.npubs.com [209.66.100.224]) by mx1.freebsd.org (Postfix) with ESMTP id D4C7A8FC13; Wed, 18 Mar 2009 17:43:50 +0000 (UTC) (envelope-from stef-list@memberwebs.com) Received: from mx.npubs.com (avhost [209.66.100.194]) by mx.npubs.com (Postfix) with ESMTP id 5D527EFB6E8; Wed, 18 Mar 2009 17:22:23 +0000 (UTC) Received: from northstar-srv2 (unknown [172.27.2.11]) by mx.npubs.com (Postfix) with ESMTP id B4B08EFB6DA; Wed, 18 Mar 2009 17:22:22 +0000 (UTC) From: Stef Walter User-Agent: Thunderbird 2.0.0.19 (X11/20090105) MIME-Version: 1.0 To: Robert Watson References: <1237299551.80881.16.camel@bauer.cse.buffalo.edu> <20090318102134.D55869@ns1.as.pvp.se> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Message-Id: <20090318172222.B4B08EFB6DA@mx.npubs.com> X-Virus-Scanned: ClamAV using ClamSMTP Date: Wed, 18 Mar 2009 17:22:23 +0000 (UTC) Cc: kama , Ken Smith , freebsd-stable Subject: Re: FreeBSD 7.2 Release process starting... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: stef@memberwebs.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Mar 2009 17:43:51 -0000 Robert Watson wrote: > One of the most important things for us to keep an eye on in this > release is that the boot loader now works on a number of pieces of > hardware on which it reressed for 6.4/7.1. If it proves successful, > we'll likely also do errata notes and roll new ISOs for 6.4. I have a machine that I updated to 7-STABLE the other day. The boot loader didn't work until I copied /boot files from an old FreeBSD. I'd like to participate in getting this fixed. Is there a place that work is being done on this? Bug reports, info needed, person to contact etc.? Cheers, Stef