Manyam wrote: >> The simple version is that you need to modify your >> DHCP to send your >> solaris clients the 'pxegrub' program from the >> solaris distribution >> instead of pxelinux, and then configure it to load a >> menu.lst file that >> will network boot solaris.. >> >> If you'd rather have the DHCP server setup to have >> all clients boot the >> same pxe executable, the pxegrub program from solaris >> can easily boot >> linux too, that's what I do. (You might be able to >> configure pxelinux to >> boot solaris too, but I've never tried.) >> >> I've never done this on the linux DHCP server, but it >> shouldn't be that >> different. If this doesn't get you started, let me >> know, and I can >> probably give more details. >> >> -Kyle >> >> > > Hi guys - I have been having trouble to automated jumpstart working with > pxelinux and solaris10 on x4200 - it seem i can boot x86 miniroot with > mcboot.c32 > > It sounds like you're going down a different road than I did. But if you can answerw few questions I still might be able to help.
1) what is mcboot.c32? and where does it come from? > this is the label i am using > > label solaris_x86 > kernel mboot.c32 > append boot/multiboot kernel/unix -v install -B console=ttya --- > boot/x86.miniroot > IPAPPEND=3 > > 2) in pxelinux, what is IPAPPEND=3 supposed to do? is it a pxelinux option? or a solaris kernel option? It looks like you want pxelinux to boot mboot.c32 which is then going to load boot/multiboot (which I think I've seen on the solaris media. Then boot/multiboot loads and boots the solaris kernel. I don't know any reason why that wouldn't work, though I don't know if the multiboot stuff in solaris is maintained since solaris GRUB stopped using it. For installs, you may want the '-v install' to be '-v - install', and for Jumpstart you probably want the '-B console=ttya' to be: -B console=ttya,sysid_config=<NFSserverIP>:/path/to/sysidcfg,install_media=<NFSserverIP>:/path/to/solaris/image,install_config=<NFSserverIP>:/path/to/jumpstart To get a hint how these might be used, run add_install_client with the -d and all the options, and then look in the grub menu file that it creates, to see how it set those other arguments to the -B option. > however i notice that netstrategy is reporting "ufs none none" (wven miniroot > is picked from solaris nevada build 90) -- and IPAPPEND does not seem to > matter > > as bootargs does not seem to get the ip/netmask info > question to the gurus: > -->doesnt netstrategy work nicely with pxelinux? > -->doesnt IPAPPEND line appended to the label above work with solaris10 > miniroot > > any info/suggestion is extremely valuable > > How grub boots solaris changed in one of the s10 updates. Solaris GRUB and the Solaris kernel used the 'multiboot' standard originally (and may still be able to use it I don't know.) but at some point, it was decided to have (teach?) grub how to boot the kernel directly (If I'm remembering right.) If you're getting the kernel to boot (and it sounds like you are) then I'd say the multiboot stuff is still there and working. Let me know how adding those other options to the kernel args goes, and maybe I'll have more ideas. -Kyle > Thanks!! > > > This message posted from opensolaris.org > _______________________________________________ > install-discuss mailing list > install-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/install-discuss >
