On Wed, 10 Dec 2008 16:31:52 -0500
"Anurag S. Maskey" <Anurag.Maskey at Sun.COM> wrote:
[...]
> Sections 7.2 and 8.2
> -------------------
>
> Going through the text/steps in Section 7.2, here's what I see is
> different with the currently implemented solution:
>
> * /var/run is /etc/svc/volatile throughout the spec.
>
> * During hard reset, the current Location is set to No-Net. This step
> is not possible during boot because the filesystem is read-only at
> this point. This can be determined by a check on the state of the
> filesystem/usr service, during boot it hasn't started yet because it
> depends on network/physical. If nwamd is doing a hard reset after a
> clean shutdown (svcadm disable nwam; svcadm enable nwam), then
> filesystem/usr is online and the No-Net Location can be installed.
>
> * After the NCP comes online, check if the filesystem/usr is online.
> If so, install the current location.
>
> * Then, if network/location is running,
> "svcadm refresh network/location"; otherwise,
> "svcadm enable -t network/location".
The second line should probably be
'svcadm clear network/location; svcadm enable -t network/location'
just in case network/location is in maintenance.
I dislike network/location coming on line only because of nwamd. This
hides part of the dependency hierarchy that users expect to be encoded
in SMF. Tools that examine that hierarchy now are blind to part of it.
>
>
> Addition to the beginning of the nwamd event loop:
>
> * If no Location has been installed (during boot), check if
> filesystem/usr is online. If so, do a Location installation.
I don't think diskless is really that big of a deal these days but this
does keep us from using NWAM with a network mounted /usr. Given a
network /usr and NWAM would be catastrophic we need to do something to
both document this issue and detect if it might be happening and warn
the user.
mph
