SUMMARY: sysidcfg for solaris 8 2/02 (fwd)

Hi,
	I just got it working yesterday.
Discovered a couple of things:
	One was that it's nice to ensure that nis
knows the netmask of the subnet.
	The other thing (probably this was the
important one) was that you have to at least fudge
or 'get around' the defaultroute requirement.  I
have a few lines of code that intelligently set
the default route in a .fin file, so I don't want
the new jumpstart requiring it in sysidcfg (makes
it impossible to have one generic sysidcfg if you
have lots of subnets, which I do).
	Anyway, check this out: for Solaris 8
02/02, you *have to* assign some sort of
defaultroute in the interface line to avoid
falling into interactive.  I did mine like this:

network_interface=primary {protocol_ipv6=no default_route=1.1.1.1}

	Note that 1.1.1.1 is totally bogus, but
this version of Solaris 8 *requires* there to be
something sane in the field and does not grok the
words "no" or "NONE" as are possible elsewhere in
the file.
	Fortunately, they wised up a bit with the
first release of Solaris 9.  Here, one must still
provide the default_route keyword, but they've
made a provision to understand the word "NONE".
Here's my entry for the Solaris 9 jumpstart:

network_interface=primary {protocol_ipv6=no default_route=NONE}


	Sorry for the late summary, but it took me
months to get around to figuring it out myself and
nobody on sunmanagers knew..

-jake

On Mon, 27 May 2002, Thomas 'Mike' Michlmayr wrote:

> hi!
>
> back in march you asked about changes to the sysidcfg file in the 2/02
> release of solaris 8 preventing automated installs. i didn't find a
> summary, so i was curious: were you able to solve your problems?
> or still no automated installs?
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers