client: searching for jumpstart directory: not found. No entry in rules file.
in [Solaris]
|
Prev: Networking to a zone - I'm stuck!
Next: client: searching for jumpstart directory: not found. No entry in ?rules file.
From: BertieBigBollox on 21 Dec 2009 07:29 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?
From: BertieBigBollox on 21 Dec 2009 08:55 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....
From: BertieBigBollox on 21 Dec 2009 09:29 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?
From: Heinz M�ller on 22 Dec 2009 08:06 "BertieBigBollox(a)gmail.com" <bertiebigbollox(a)gmail.com> schrieb im Newsbeitrag news:906c2c3f-802d-43f8-9c6b-8f43aaf1a81a(a)a32g2000yqm.googlegroups.com... > 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? Check if the share is set correct(ly) on the jumpstartserver. Heinz
From: phil.googlenews on 24 Dec 2009 14:50
On Dec 23, 1:52 pm, Cydrome Leader <prese...(a)MUNGEpanix.com> wrote: > By using a non-sun DHCP server, we finally got a kernel to boot. rules > never worked, ever. Nobody at sun could get it to work either, which > doesn't surprise me as they keep changing all the secret paramaters and > settings every 9 seconds with their junior attempts as PXE booting. > > To this day, there's still no accurate or even close to upto date doc on > jumpstarting sun stuff with PXE where the commands as they show actually > work. There's some "blueprint" from 2006 or so. it's completely useless. FYI: I had some problems in that area myself. I discovered by a lot of trial and error, that #1. it doesnt like subdirectories for profiles. has to be in same dir as rules file. (Same problem with using WANBOOT on sparc now!!!) #2. I gave up on regular rules/profile sharing for PXE/sol x86,and went to a little known method of using a tarfile. My grub entries look like the following: title 6 Solaris 10 net install experimental tarcfg, serial console kernel /boot/200810/multiboot kernel/unix - install nfs://x.x.x.x /jumpstart/jumpstart.tar -B console=ttya,install_media=nfs://x.x.x.x/ jumpstart/s10x86200810 module /boot/200810/x86.miniroot Even WANBOOT, ugly as it it, would be an improvement over this mess. Dammit sun, pick a technology and STANDARDIZE!! Tips: "/boot" entries, are references to a subdir in /tftpboot jumpstart.tar is created by a Makefile in the jumpstart dir that looks like the following: FILES = README rules rules.ok sysidcfg *.prof begin_* finish_* jumpstart.tar: $(FILES) tar cvf jumpstart.tar $(FILES) |