Dave Miner wrote:
> 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?
>>
>
> The domain name is only returned as part of the bootparams WHOAMI 
> call, and that's only done if the system is booted using RARP; see
>
> http://src.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/stand/lib/fs/nfs/mount.c#558
>  
>
>
> Using a sysidcfg file would seem to be the solution you're looking for.
>
Yeah. :( That works, but it's the solution I try to avoid at all costs.
I think I'd rather hack install-discovery to reenable the dhcp-options.

Dave do you know where I can find a pre-newboot copy of 
install-discovery, to diff and see the changes made for newboot?
(or where I can find the diff if it might exist already?) the source 
history for install-discovery isn't on os.org is it?

  -Kyle

> Dave


Reply via email to