From owner-freebsd-bugs Tue May 7 18:48:19 2002 Delivered-To: freebsd-bugs@freebsd.org Received: from bastion2.act.csiro.au (bastion2.act.csiro.au [152.83.2.9]) by hub.freebsd.org (Postfix) with ESMTP id 38EAF37B419; Tue, 7 May 2002 18:47:54 -0700 (PDT) Received: from bastion2.act.csiro.au (localhost [127.0.0.1]) by bastion2.act.csiro.au (8.11.4/8.11.4) with ESMTP id g481lq501029; Wed, 8 May 2002 11:47:52 +1000 (EST) Received: from hermes.la.csiro.au (hermes.la.csiro.au [152.83.12.2]) by bastion2.act.csiro.au (8.11.4/8.11.4) with ESMTP id g481lq801025; Wed, 8 May 2002 11:47:52 +1000 (EST) Received: by hermes.la.csiro.au with Internet Mail Service (5.5.2653.19) id ; Wed, 8 May 2002 11:47:52 +1000 Message-ID: <4ABEF4D887D40745B8D6804C2FFA939F1A75EF@hermes.la.csiro.au> From: Anthony.Wyatt@csiro.au To: Freebsd-bugs@freebsd.org, Freebsd-config@freebsd.org Subject: Pushing the boot process past its limits Date: Wed, 8 May 2002 11:47:50 +1000 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi All, For all those that are going to flame me for cross posting this email, I know, I'm evil and I will repent later today :-) Quick Background: I decided that I want to build a boot CD that will load my FreeBSD image into a ram drive and run from there. I've so far managed to embed my mfs file into my kernel and it all boots fine (for a 3M mfs root partition). What I would really like to do is have the mfs file on the root of the CD and load it from /boot/loader at boot time, I don't seem to be able to see the FS on the CD, on the FS on the boot image. So I started playing around. I've created a 128M mfs file and stuffed it into my kernel, so far so good. I've compressed it and it fits on the 2.88M floppy image that I use as the boot image for the CD, but weird things happen when I boot (I'm using Vmware with 256M of memory, I've tried this with 384M config also): BTX loader 1.00 BTX version is 1.01 Console: internal video/keyboard BIOS drive A: is disk0 BIOS drive B: is disk1 BIOS drive C: is disk2 BIOS 638kB/261129kB available memory FreeBSD/i386 bootstrap loader, Revision 0.8 (root@primary, Sun May 5 22:09:02 EST 2002) \ Hit [Enter] to boot immediately, or any other key for command prompt. Booting [kernel]... /kernel text=0x1760 data=0x1397f6+0x1050e syms=[0x4+0x490+0x4+0x203] / int=00000006 err=00000000 efl=00000003 eip=10000000 eax=082de0e8 ebx=00000000 ecx=ffffffff edx=00027480 esi=00000000 edi=08421f80 ebp=0009e5ec esp=0009e5d8 cs=0008 ds=0010 es=0010 fs=0010 gs=0010 ss=0010 cs:eip=ff ff ff ff ff ff ff ff-ff ff ff ff ff ff ff ff ss:esp=1b f3 2d 00 00 00 00 00-80 1f 42 08 00 00 00 00 BTX halted What does this mean? Is there a better way of constructing a FS in memory from boot? Is this a bug, or just outside the design of the boot procedures? Is there a way to load a mfs file off a CD from boot and not from the floppy boot image on the CD? Thanks for your time, Anthony To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message