On 06/08/12 15:14, Brock Pytlik wrote:
On 06/08/12 14:17, Mike Gerdts wrote:
On 06/08/12 15:16, Brock Pytlik wrote:
On 06/08/12 06:49, Mike Gerdts wrote:
On 06/07/12 22:13, Brock Pytlik wrote:

[snip]
In all of the above, it seems as though you aren't using image
names, rather you are using zone names. -Z evokes "zone". Thus, it
shouldn't be "root", it should be "global". This avoids the problems
associated with a zone named "root".

That does bring up another issue. Is there intent to allow user
images to be linked to a system image? If so we probably need a way
to distinguish between user images and system images because user
images are unlikely to be participate in this scheme that is clearly
aimed at zones.

No, I actually do mean image names. I'm not sure what about the names
implies they're zones and not images. If it's that they don't all
begin with "system:" or "linked:" or whatever the tag is, my hope was
that we could make an educated inference about what kind of image
they meant 99.9% of the time, and not make them type the same prefix
over and over and over.
I wasn't aware that images had names. For some strange reason, I was
also thinking that -Z meant zone rather than zChildImage (forgot about
the silent z...) :).

:) Yeah, I thought about -I, but we already have that option, though
undocumented and at the subcommand level, but since it has a meaning
that I thought was nearly opposite of what we wanted, I thought that
wasn't a good choice. Perhaps -i?

I think the issue is that with all of the zone utilities, -z refers to the name of the zone, so that's going to be a hard thing to get out of people's heads, and they're also likely going to keep typing '-z' instead of '-Z' since that's how the zone utilities also work.

-C would have been nice here for 'child', but Ed has stolen that for concurrency.

Personally, I'd just punt on the more generic child images case and just handle zones. If we do that though, that would suggest we use '-z' for consistency with the zone utilities.

-Shawn
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss

Reply via email to