jumpstart sysidcfg issue
in [Solaris]
|
Prev: client: searching for jumpstart directory: not found. No entry in ?rules file.
Next: disaster recovery for a host with zones
From: Gary Mills on 22 Dec 2009 09:19 In <743fa8f9-fc0e-4a41-841e-4c58b6775b45(a)m3g2000yqf.googlegroups.com> prkrol <prkrol(a)gmail.com> writes: >I've lost whole day searching why my jumpstart config is not using >desired sysidcfg file. For SPARC with RARP, we specify the sysidcfg directory in the bootparams map: install=dvdhost:/jump/S10_up1009_cd term=nfshost:sun boottype=:in root=dvdhost:/jump/S10_up1009_cd/Solaris_10/Tools/Boot install_config=nfshost:/vol/vol1/special/install_config/S10_config sysid_config=nfshost:/vol/vol1/special/install_config/S10_config rootopts=:rsize=32768 For x86 with DHCP, we specify it in the GRUB menu: title S10_up1009 Jumpstart ttya console install (X4100) kernel /I86PC.S10_up1009/multiboot kernel/unix - install -B install_media=AAA.BBB.CC.DD:/jump/S10_up1009_x86_cd,install_config=AAA.BBB.CC.EE:/vol/vol1/special/install_config/S10_config,sysid_config=AAA.BBB.CC.EE:/vol/vol1/special/install_config/S10_config,console=ttya module /I86PC.S10_up1009/x86.miniroot -- -Gary Mills- -Unix Group- -Computer and Network Services-
From: prkrol on 22 Dec 2009 15:55 Thanks for reply. I found where was my problem - basing on my week memory :-S I in boot command I was using "boot net:dhcp - -install", i dont know from where I got that, I was sure its correct... Of course valid syntax is "boot net:dhcp - install" and everything is warking like charm Sorry for false alarm :( -- regards Przem
From: Cydrome Leader on 22 Dec 2009 19:53 Gary Mills <mills(a)cc.umanitoba.ca> wrote: > In <743fa8f9-fc0e-4a41-841e-4c58b6775b45(a)m3g2000yqf.googlegroups.com> prkrol <prkrol(a)gmail.com> writes: > >>I've lost whole day searching why my jumpstart config is not using >>desired sysidcfg file. > > For SPARC with RARP, we specify the sysidcfg directory in the > bootparams map: > > install=dvdhost:/jump/S10_up1009_cd term=nfshost:sun boottype=:in root=dvdhost:/jump/S10_up1009_cd/Solaris_10/Tools/Boot install_config=nfshost:/vol/vol1/special/install_config/S10_config sysid_config=nfshost:/vol/vol1/special/install_config/S10_config rootopts=:rsize=32768 > > For x86 with DHCP, we specify it in the GRUB menu: > > title S10_up1009 Jumpstart ttya console install (X4100) > kernel /I86PC.S10_up1009/multiboot kernel/unix - install -B install_media=AAA.BBB.CC.DD:/jump/S10_up1009_x86_cd,install_config=AAA.BBB.CC.EE:/vol/vol1/special/install_config/S10_config,sysid_config=AAA.BBB.CC.EE:/vol/vol1/special/install_config/S10_config,console=ttya > module /I86PC.S10_up1009/x86.miniroot > you have to admit, these command and parameters are so long and complex they're just stupid. Sun, you get an F
From: Richard B. Gilbert on 22 Dec 2009 20:09 Cydrome Leader wrote: > Gary Mills <mills(a)cc.umanitoba.ca> wrote: >> In <743fa8f9-fc0e-4a41-841e-4c58b6775b45(a)m3g2000yqf.googlegroups.com> prkrol <prkrol(a)gmail.com> writes: >> >>> I've lost whole day searching why my jumpstart config is not using >>> desired sysidcfg file. >> For SPARC with RARP, we specify the sysidcfg directory in the >> bootparams map: >> >> install=dvdhost:/jump/S10_up1009_cd term=nfshost:sun boottype=:in root=dvdhost:/jump/S10_up1009_cd/Solaris_10/Tools/Boot install_config=nfshost:/vol/vol1/special/install_config/S10_config sysid_config=nfshost:/vol/vol1/special/install_config/S10_config rootopts=:rsize=32768 >> >> For x86 with DHCP, we specify it in the GRUB menu: >> >> title S10_up1009 Jumpstart ttya console install (X4100) >> kernel /I86PC.S10_up1009/multiboot kernel/unix - install -B install_media=AAA.BBB.CC.DD:/jump/S10_up1009_x86_cd,install_config=AAA.BBB.CC.EE:/vol/vol1/special/install_config/S10_config,sysid_config=AAA.BBB.CC.EE:/vol/vol1/special/install_config/S10_config,console=ttya >> module /I86PC.S10_up1009/x86.miniroot >> > > you have to admit, these command and parameters are so long and complex they're just stupid. > > Sun, you get an F Since the Solaris source is available, you can do it the "right way" and, if you wish, contribute it to help deconfuse the next guy!
From: YTC#1 on 23 Dec 2009 07:43
On Wed, 23 Dec 2009 00:53:38 +0000, Cydrome Leader wrote: > Gary Mills <mills(a)cc.umanitoba.ca> wrote: >> In <743fa8f9-fc0e-4a41-841e-4c58b6775b45(a)m3g2000yqf.googlegroups.com> prkrol <prkrol(a)gmail.com> writes: >> >>>I've lost whole day searching why my jumpstart config is not using >>>desired sysidcfg file. >> >> For SPARC with RARP, we specify the sysidcfg directory in the >> bootparams map: >> >> install=dvdhost:/jump/S10_up1009_cd term=nfshost:sun boottype=:in root=dvdhost:/jump/S10_up1009_cd/Solaris_10/Tools/Boot install_config=nfshost:/vol/vol1/special/install_config/S10_config sysid_config=nfshost:/vol/vol1/special/install_config/S10_config rootopts=:rsize=32768 >> >> For x86 with DHCP, we specify it in the GRUB menu: >> >> title S10_up1009 Jumpstart ttya console install (X4100) >> kernel /I86PC.S10_up1009/multiboot kernel/unix - install -B install_media=AAA.BBB.CC.DD:/jump/S10_up1009_x86_cd,install_config=AAA.BBB.CC.EE:/vol/vol1/special/install_config/S10_config,sysid_config=AAA.BBB.CC.EE:/vol/vol1/special/install_config/S10_config,console=ttya >> module /I86PC.S10_up1009/x86.miniroot >> > > you have to admit, these command and parameters are so long and complex they're just stupid. > They are just a means of passing detail to the client. A bit like was done via bootparams. I appreciate that PXE boot differs from bootp, I had a lot of problems getting there myself. But once you accept it is just a different way to achive the same result, and are happy to utilise a decent tool (JET) to get there then there are no problems. -- Bruce Porter "The internet is a huge and diverse community and not every one is friendly" http://www.ytc1.co.uk There *is* an alternative! http://www.openoffice.org/ |