On 3/18/06, Sven Luther <sl at bplan-gmbh.de> wrote: > > 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>
Hi, Sven, The inetboot parse bootpath and bootargs and pass most of them to the kernel, but not for the static configuration of the network. inetboot network are within subnet, so all needed network config is the ip and rarp is enough. yet dhcp is generally available so no need to setup server ( I will see how to force inetboot to use dhcp). In general, network configuration of inetboot is not very much platform dependent and it is a matter of programming to use different features, either rarp(dhcp)/bootparamd or bootpd or static configuration. Noah or the rarp/bootp/dhcp version of this one. > > Friendly, > > Sven Luther > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/pipermail/powerpc-discuss/attachments/20060320/8aef66a8/attachment.html>
