client: searching for jumpstart directory: not found. No entryin rules file.
in [Solaris]
|
Prev: client: searching for jumpstart directory: not found. No entry in ?rules file.
Next: client: searching for jumpstart directory: not found. No entry in ??rules file.
From: Richard B. Gilbert on 21 Dec 2009 08:22 BertieBigBollox(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?
From: Richard B. Gilbert on 21 Dec 2009 09:13 BertieBigBollox(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.... The documentation at this link: http://docs.sun.com/app/docs/doc/821-0439 might be of some help.
From: Richard B. Gilbert on 21 Dec 2009 09:14 BertieBigBollox(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
From: Richard B. Gilbert on 21 Dec 2009 10:01 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.
From: Richard B. Gilbert on 21 Dec 2009 22:10
Cydrome Leader wrote: > 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. > If Jumpstart fails to work as documented, you need to complain to Sun. I don't know how seriously they take reports/complaints from people who are not paying customers. I'm fairly sure that they will fix it someday. I couldn't even attempt to guess what priority the problem would be given unless the complaint came from a customer paying support. OTOH, Jumpstart is not particularly useful unless you are installing two or more machines. The more machines you have to install the more valuable it is. If you are installing one system just put the DVD in the drive and boot from it! Be ready to supply the IP address, netmask, node name, and timezone for the machine you are installing. You will also be asked for the current date and time. There is nothing particularly arcane about the installation. It's mostly waiting for the next time your input is required. You will be asked how to partition the disk. Allow at least 4GB for / plus /usr. Allow another 4GB for /var. If you have reason to think you will need more, go ahead and allocate more. Disk space is relatively cheap. You will also be asked if you want to install everything or not. Unless you are VERY certain that you do not want to install some part of Solaris just go ahead and install everything. If you don't you will probably regret it later. Adding pieces of the O/S later requires that you know what all the dependencies are. While you can figure it out, you'll wish you had done the full install. |