> Rick Miller wrote: > > Ok. I had a conversation with the developer to get > a more full explanation of what was going on in his > application. The developer is using pxelinux to load > the comboot module (mboot.c32) which executes the > in-house boot loader. The in-house boot loader, > therefore, is based on pxelinux. The in-house boot > loader executes the following on the mboot.c32 > module: > > > > Kernel: mboot.c32 > > Append: -solaris multiboot-solaris-10u7-x86 > kernel/unix -B > install_media=$ip_addr:$dir,install_config=$ip_addr:$d > ir - install nowin --- x86.miniroot > > > > With this knowledge, it seems to me that the -B > boot args are being dropped between mboot.c32 and the > OS kernel. So, now the question then becomes 'how do > I determine where?' Does all this sound logical or > am I blowing smoke out my tailpipe? :) > > > I don't know if it matters or not, but all of the > kernel arg lists I use > have: > > .../unix - install nowin -B > install_media=...,install_config=...,... > > Is the way you list it above the way you did it > before it broke? Or did > it change? > > -Kyle
Thanks for the reply, Kyle. The kernel arguments (- install nowin) we had previously had appended to the end of the boot args and before the "--- x86.miniroot". It had worked previously. I also ran a test positioning it the way you have described and that produced the same results. I just came across a post on unix.com where someone is actually passing "dhcp" in the kernel boot arguments and I am wondering if it's necessary for me to also do the same. Afterall, when the OS kernel loads and proceeds to setup the interfaces, it doesn't even try to dhcp an address, presumably because netstrategy returns "ufs none none". -- This message posted from opensolaris.org
