On 06/ 2/10 03:03 AM, [email protected] wrote:
On (06/01/10 13:42), Edward Pilatowicz wrote:
hey sowmini,
so i had some concerns about one small bit below...
:
i'm concerned about the "on the first boot" bit above. i think that
condition may be hard to detect due to zones life cycle. some examples:
- if a detach and attach a zone and then boot it, is that a first boot?
- if a detach and attach a zone on another host and then boot it, is
that a first boot?
- if a install a zone via cloning of another zone and then boot it, is
that a first boot?
The "first boot" state is actually detected by an internal private property
inside ipmgmtd/ipadm, and the property is initialized exactly once.
So the latter 2 cases would constitute a "first boot" whereas the first
one would not.
I don't understand hoe #2 and #3 can be viewed as "first boot" since the
ipadm persistent properties are stored in the ngz hence are as preserved
as the zone is moved.
The desired behavior is that "first boot" applies in the same cases as
where the ngz looks for sysidcfg, i.e., on the first boot after install
of the zone (where cloning is merely a particular way to install a zone).
Note that for the cloned zones case (3rd one above) we have a bug in
that sys-unconfig doesn't know about persistent ipadm (and dladm)
information, but does know about /etc/hostname files.
If sys-unconfig is taught that, and the result of sys-unconfig is to
remove all the persistent ipadm properties including this private "first
boot" property, then we'd end up with behavior that is self-consistent.
Erik
_______________________________________________
opensolaris-arc mailing list
[email protected]
