On Sat, Mar 18, 2006 at 01:30:38PM -0600, Noah yan wrote: > Hi Sven, > > I forget to mention this. Currently, the root file system is just an > exported directory, nothing in it. You can put an ELF binary (as kernel) > that can bootstrap itself, such as grub, or linux kernel, or even the > inetboot.elf itself. When the inetboot.elf is loaded and runs, it will > prompt to ask for the kernel (default is ppc/unix), just input the name of > the file that is put in the nfs root (be sure to start with "/"). and the > inetboot will load it and transfer control to it.
Ah, nice. I guess the real test will be when we will be able to do the same, but instead of using inetboot and rarp/bootp/dhcp/nfs, we will be able to use the client read interface to access the filesystem. Do you know what inetboot.elf uses ? Does it parse the chosen/bootpath node, and uses that. It would be interesting then to have it be able to parse either the static stuff : boot eth:<server-ip>,<file>,<own-ip>,<gateway-ip>,<netmask> or the rarp/bootp/dhcp version of this one. Friendly, Sven Luther
