Hi Kyle, You shouldn't need to use rpc.bootparamd at all.
My menu.lst looks like this: menu.lst.01001DE00F91E2: kernel /I86PC.Solaris_11-6/platform/i86pc/kernel/unix - install nowin -B install_config=192.168.1.3:/opt/SUNWjet,sysid_config=192.168.1.3:/opt/SUNWjet/Clients/fred,install_media=192.168.1.3:/export/install/iso/Solaris_11_b90x,install_boot=192.168.1.3:/export/install/iso/Solaris_11_b90x/boot The NIS config is in the sysidcfg. Mike Kyle McDonald wrote: > Dave Miner wrote: > >> Kyle McDonald wrote: >> >>> Dave Miner wrote: >>> >>>> Kyle McDonald wrote: >>>> >>>>> On X86 NV b90, How does rpc.bootparamd know what NIS domainname to >>>>> pass to the client. >>>>> >>>>> the ns= directive in /ec/bootparams doesn't seem to have a way to >>>>> specify the domainname. >>>>> >>>>> >>>> There's a nice comment which explains it at line 110 of the below: >>>> >>>> http://src.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/cmd/rpcsvc/rpc.bootparamd/bootparam_subr.c >>>> >>>> >>>> >>>> Dave >>>> >>> Thanks Dave. >>> >>> Unfortunately none of those 3 things are happening at all. >>> >>> The bootparam server is the NIS server, it has had it's domain name >>> set all along. >>> Originally I didn't have a ns=:nis line in /etc/bootparams (which >>> always worked in the past,) but even when I added it it didn't help. >>> >>> I've also tried a domain=Engineering.NIS line, both with and without >>> the ns=:nis line. Nothing seems to help. >>> I'm running rpc.bootparamd in debug mode and I'm only seeing the one >>> get_file1 call. >>> >>> I though it might have to do with me putting all the Jumpstart NFS >>> info into the GRUB menu.lst file, so I backed that out so that the >>> kernel line just has '- install' and -B options for the serial >>> console. That complains that the Install media not being found (even >>> though I did add all of that to the /etc/bootparams) and snoop and >>> rpc.bootparamd don't show any requests at all from the client. >>> >>> Any ideas? >>> >>> >> Clearly, the issue is that the client never asks, which I'd expect >> since you're using PXE to boot it. Bootparams requests always went >> with RARP, not DHCP. >> >> > Ok. Maybe, but then this is broken somehow... > > If I do '- install dhcp', getting the info (that I used distribute with > rpc.bootparamd) from DHCP doesn't work since Sun disabled that over(?) a > year ago. > If I do '- install -B install_config=...,install_media=...' then I get > prompted for the locale, terminal_type, nameservice, and domain name. > > So I tried to do '- install -B install_config=,install_media=...' with > rpc.bootparamd helping out to configure the nameservice automatically. > And even though I'm using PXE, the netboot does make a bootparams > request - I see it in the debug output - and if I have the 'ns=:nis', > receives an answer for the type of namesservice (NIS), but not the > domain name. I can tell because after the locale menu, and the terminal > menu, when the nameservice configuration screen comes up, NIS is already > "X'd" whereas without the 'ns=:nis' the default is to "X" NIS+. > > So if that RPC to rpc.bootparams is asking for and getting 'NIS'.... Why > doesn't the response include the domain name? > > -Kyle > > >> Dave >> >> > > _______________________________________________ > install-discuss mailing list > install-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/install-discuss > -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3237 bytes Desc: S/MIME Cryptographic Signature URL: <http://mail.opensolaris.org/pipermail/install-discuss/attachments/20080611/0de05736/attachment.bin>
