Date: Wed, 19 Feb 2003 13:04:19 -0500 (EST) From: Andrew Gallatin <gallatin@cs.duke.edu> To: Sean_Welch@alum.wofford.org Cc: grehan@FreeBSD.ORG, freebsd-ppc@FreeBSD.ORG Subject: Re: Also interested in testing Message-ID: <15955.50979.366413.172143@grasshopper.cs.duke.edu> In-Reply-To: <166439.1045677133482.JavaMail.nobody@fozzie.psp.pas.earthlink.net> References: <166439.1045677133482.JavaMail.nobody@fozzie.psp.pas.earthlink.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?15955.50979.366413.172143>