From owner-freebsd-ppc Wed Feb 19 13:20:32 2003 Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 86D1337B405; Wed, 19 Feb 2003 13:20:29 -0800 (PST) Received: from swan.mail.pas.earthlink.net (swan.mail.pas.earthlink.net [207.217.120.123]) by mx1.FreeBSD.org (Postfix) with ESMTP id DC5A143F3F; Wed, 19 Feb 2003 13:20:26 -0800 (PST) (envelope-from welchsm@earthlink.net) Received: from fozzie.psp.pas.earthlink.net ([207.217.78.218]) by swan.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 18lbdh-0003w6-00; Wed, 19 Feb 2003 13:20:25 -0800 Received: from [207.217.78.205] by EarthlinkWAM via HTTP; Wed Feb 19 13:20:25 PST 2003 Message-ID: <5035103.1045689625512.JavaMail.nobody@fozzie.psp.pas.earthlink.net> Date: Wed, 19 Feb 2003 13:20:23 -0600 (GMT) From: Sean Welch Reply-To: Sean_Welch@alum.wofford.org To: Andrew Gallatin Subject: Re: Re: Also interested in testing Cc: grehan@FreeBSD.ORG, freebsd-ppc@FreeBSD.ORG Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Earthlink Web Access Mail version 3.0 Sender: owner-freebsd-ppc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Please forgive my ignorance -- my understanding of the boot process is minimal at best. I think you mean that you have the program loader (found under /boot on a FreeBSD system) in the OS X partition (slice?). You then run that from OF and tell it where the FreeBSD slice is so that it can boot the kernel. This makes sense to me. The next part contradicts my understanding of the process... You said you can boot the kernel directly -- that sounds as though you bypass the loader program altogether, but how do you specify the slice and root partition of the rest of the system? If it starts directly from the OS X slice it can't infer that, can it? I know that the command "boot -a" will let you specify this in response to a question, but I thought that "boot" was calling the entire bootstrapping sequence, including loader? This is good stuff -- the porting effort is obviously much further along than I had hoped! Sean -------Original Message------- From: Andrew Gallatin Sent: 02/19/03 12:04 PM To: Sean_Welch@alum.wofford.org Subject: Re: Also interested in testing > > Sean Welch writes: > someone mentioned "compiling natively;" does this mean > something along the lines of net booting and then using > either an NFS mounted disk or a local disk for compiling > a kernel? What can I do to duplicate this? Are there > ISO images or do need to set up an NFS server for my > efforts? I managed (a month or so ago) to build a kernel natively and boot it. Eg, the source was in a local fs on my powerbook, and the resulting kernel was copied to / and booted. Here's my story (remember, its been one month, so details may be a little fuzzy): I left a 9GB Apple partition free on my powerbook when I installed it with 10.2. I netbooted FreeBSD using a cross-built kernel and world (built on my x86 desktop). I then newfs'ed that partition and copied FreeBSD onto it. This left me with a machine I needed to netboot (openfirmware doesn't grok UFS). Fortunately, you can slap /boot/loader into an HFS+ partition (using a 3rd machine to copy the file to; reboot into MacOS, copy the file back). Then you can boot directly from openfirmware. Once you get to the loader, you can set the curdev to be the FreeBSD partition, then load the kernel and away you go. Its somewhat easier to just copy the kernel to the HFS+ partition and boot it directly. Hope that helps.. Drew > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ppc" in the body of the message