Prev: client: searching for jumpstart directory: not found. No entry in ?rules file.
Next: disaster recovery for a host with zones
From: Cydrome Leader on 23 Dec 2009 09:32
Richard B. Gilbert <rgilbert88(a)comcast.net> wrote:
> 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!

I'm not on sun's payroll and therefore I don't write code for them.

Until then, my free advice to sun is forget how they did stuff in the
1980s, and take some notes from IBM and Microsoft on how network attached
should behave.

First  |  Prev  | 
Pages: 1 2
Prev: client: searching for jumpstart directory: not found. No entry in ?rules file.
Next: disaster recovery for a host with zones