From: Cydrome Leader on
In alt.solaris.x86 Richard B. Gilbert <rgilbert88(a)comcast.net> wrote:
> BertieBigBollox(a)gmail.com wrote:
>> On Dec 21, 2:14 pm, "Richard B. Gilbert" <rgilber...(a)comcast.net>
>> wrote:
>>> BertieBigBol...(a)gmail.com wrote:
>>>> On Dec 21, 1:22 pm, "Richard B. Gilbert" <rgilber...(a)comcast.net>
>>>> wrote:
>>>>> BertieBigBol...(a)gmail.com wrote:
>>>>>> Any ideas what to check....
>>>>>> /etc/bootparams seems to be doing its job because client boots up ok
>>>>>> and seems to find the correct sysidcfg.
>>>>>> However, for some reason its saying rules is wrong.
>>>>>> What to check first?
>>>>> Your rules file?
>>>> BTW. Should mention it is there....
>>> Is are the contents syntactically and semantically correct?
>>>
>>> I dimly recall that there are two files involved: sysidconfig is one and
>>> the other is your rules file.
>>>
>>> The "Advanced Installation Manual" goes into all this in some detail
>>
>> Thing is I saved a few of the files and the complete /jumpstart
>> directory off another working js server.
>>
>> It seems to find the correct profile and then fail to find the
>> jumpstart directory? Weird - because I think I'm right in saying this
>> is all identified in the bootparams file, isnt it?
>>
>
> Don't know! The one time in my career that it would have been useful, I
> hadn't a clue. Somebody showed me how to install from the local CD
> drive. I repeated the steps for eight machines, one at a time. Since
> then I've read TFM but had no need to do mass installations.
>
>
> The best advice I can give you is RTFM and follow the directions.

jumpstart is picky and overly complex monster. On x86, it's just
worthless.

always add the -v flag to your boot install whatever command so you can
see what's happening and where it blows up.

You're at least able to get an address, and boot the kernel off your
jumpstart machine if you're getting rules errors- this is good.