In <m390ihfa4v.fsf_-_@trantor.cosmic.com>,
mirian@xensei.com wrote:

 > I've noticed that it takes about 6 hours to compile the netbsd-current
 > kernel from scratch.  Of course, this IS an early-model BeBox, with
 > only PPC 603 processors (and only two of them), so perhaps this is
 > normal.  I have 48 Megs of RAM in the thing, and it isn't paging, so
 > it must really just be that slow.

A performance is one of what we must improve.

 > So, I have a few questions (well, actually only one, for now):
 > Is there a way to bootstrap my IDE disk so that I can boot netbsd
 > without a floppy?  I don't see installboot in the bebox shapshot.

It is possible if bfs(BeOS filesystem) is made in IDE disk
and boot.pef is put there.

	NetBSD:
		cd arch/bebox/stand/boot
		make
		 boot.pef => floppy or other computer via network

	BeOS:
		cd (IDE disk mount point)
		mkdir system
		 boot.pef <= floppy or other computer via network
		cp boot.pef system/kernel

But, this bootloader can read kernel only from floppy disk.
If interface of the BeBox's BootROM is opened to the public,
I think that it can be solved. Or, we will make standalone IDE/SCSI 
disk driver.

So, I made the method attach kernel to bootloader
(I got a hint from BootLoader of NetBSD/macppc).
Please read arch/bebox/stand/boot/Makefile.


Reference:

How the Be OS Starts Up - Be Newsletter Issue 5
http://www.be.com/aboutbe/benewsletter/Issue05.html#anchor461869

OS Writer's Cookbook - Be Newsletter Issue 27
http://www.be.com/aboutbe/benewsletter/Issue27.html#Cookbook


 > Anyway, now that I'm finally set up, I'm ready to start hacking on the
 > code.

Let's go!

Kazuki Sakamoto
sakamoto@cec.co.jp