From owner-freebsd-current@FreeBSD.ORG Tue Jan 31 18:52:19 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 06B7116A422 for ; Tue, 31 Jan 2006 18:52:19 +0000 (GMT) (envelope-from julian@elischer.org) Received: from a50.ironport.com (a50.ironport.com [63.251.108.112]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3D9E443D53 for ; Tue, 31 Jan 2006 18:52:12 +0000 (GMT) (envelope-from julian@elischer.org) Received: from unknown (HELO [10.251.17.229]) ([10.251.17.229]) by a50.ironport.com with ESMTP; 31 Jan 2006 10:52:13 -0800 Message-ID: <43DFB1DC.2020001@elischer.org> Date: Tue, 31 Jan 2006 10:52:12 -0800 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.11) Gecko/20050727 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <200601311502.k0VF2uGP054807@lurza.secnetix.de> In-Reply-To: <200601311502.k0VF2uGP054807@lurza.secnetix.de> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: boot block differences between 4.x and 6.x ? 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 Jan 2006 18:52:19 -0000 Oliver Fromme wrote: >Luigi Rizzo wrote: > > the revised picobsd script (attached here, it uses > > sysutils/makefs instead of vnconfig/mdconfig so it can > > run as a non privileged user) that i was using to > > create images with the 4.11 boot blocks (boot1 and boot2), > > does not seem to work anymore with the boot blocks > > taken from 6.0 (and so, -current as well). > > > > When i force it to use the 4.x boot blocks, all is fine, > > and the picobsd.bin produced (built on 6.0 using 7-current > > sources) boots fine on qemu. > >FWIW, a standard 4-stable system boots fine with the boot >blocks (and loader) from RELENG_6. I'm running such a >mixed system: /boot/* and boot blocks from RELENG_6, and >everything else from RELENG_4. > >I think the most visible changes in the boot blocks was >UFS2 support and the removal of nextboot(8) support. > > which I hope to put back because we continue to need it. (The new nextboot being dependent on the root filesystem still being ok which is unacceptable to most embedded devices I've worked on, and why we still use the old bootblocks on all systems shipped.). >Best regards > Oliver > > >