From owner-freebsd-current@FreeBSD.ORG Tue Jan 31 14:44:03 2006 Return-Path: X-Original-To: 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 2989B16A420 for ; Tue, 31 Jan 2006 14:44:03 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6A83443D73 for ; Tue, 31 Jan 2006 14:44:01 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (junior.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id k0VEi06D018313; Tue, 31 Jan 2006 07:44:00 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <43DF77B7.4050800@samsco.org> Date: Tue, 31 Jan 2006 07:44:07 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20051230 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Luigi Rizzo References: <20060131061812.A53329@xorpc.icir.org> In-Reply-To: <20060131061812.A53329@xorpc.icir.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on pooker.samsco.org Cc: current@freebsd.org 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 14:44:03 -0000 Luigi Rizzo wrote: > maybe some of you know the answer here... > > 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. > > I am a bit puzzled on what could be the relevant change in boot1/boot2 > could have caused the loss of functionality. > > If that matters, picobsd bypasses /boot/loader and goes straight > to boot /kernel (the name is patched into the boot block, > but it does not matter because the new blocks do not > even get to the point of showing the 'missing /boot/loader' > error message). > > does anyone know where should i look at ? > > thanks > luigi > The big difference is that the boot blocks grew significantly to support UFS2. Scott