From owner-freebsd-current@FreeBSD.ORG Tue Jan 31 15:59:39 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 DC0D616A422 for ; Tue, 31 Jan 2006 15:59:39 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 48DE043D45 for ; Tue, 31 Jan 2006 15:59:39 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1] (may be forged)) by harmony.bsdimp.com (8.13.3/8.13.3) with ESMTP id k0VFvrfW033277; Tue, 31 Jan 2006 08:57:56 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Tue, 31 Jan 2006 08:58:04 -0700 (MST) Message-Id: <20060131.085804.96587431.imp@bsdimp.com> To: scottl@samsco.org From: "M. Warner Losh" In-Reply-To: <43DF77B7.4050800@samsco.org> References: <20060131061812.A53329@xorpc.icir.org> <43DF77B7.4050800@samsco.org> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Tue, 31 Jan 2006 08:57:56 -0700 (MST) Cc: rizzo@icir.org, 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 15:59:40 -0000 In message: <43DF77B7.4050800@samsco.org> Scott Long writes: : 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. And boot1/boot2 were merged into boot... Warner