Miller, Vincent (Rick) wrote: >> 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:$dir - 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. > Oh. I always understood it to be: .../unix <kernel args> - <parameters passed to things run by init>
So kernel args are things lik -k, -v, -s, and -d, and 'install', 'nowin', 'dhcp' and -B ... are all passed on to init, and programs that init runs, to be processed later. I'm guessing the --- is a pxelinux specifc option to separate the kernel args from the initrd (miniroot)?? In pxegrub I put the miniroot filename as anrgument to the 'module' option, not to the 'kernel' option. What version of S10 were you using earlier? and what version are you moving to? > 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". > The 'dhcp' arg was used early on in X86 (and still is on SPARC) to get the install_media, install_config, etc. parameters from Sun Vendor specific DHCP options. If configured them that way, then you wouldn't need to add them to the -B option list. 'dhcp' stopped having any effect on X86 after s10u1 I think (which pissed me off since now I have to maintain several menu.lst files, instead of including predefined OS macros's into the host macro of each client in the DHCP server.) The install client should still get it's IP and other info from DHCP even with out the 'dhcp' boot argument. I don't know what else to suggest, sorry. -Kyle
