I went back and forth with th bug pertaining the [-x nodataset] option

6880288 zoneadm install -x nodataset option should be brand-specifc

and eventually I decided to ask for quorum to just bury this option

When Jerry filed it, his intent was to make it brand specific
as that option means no zfs dataset should be created for a zoneroot.
the zone will be just put onder a zoneroot directory instead.

this really only makes sense for native brands that do not rely on all
the fancy beadm/ips features used in OSOL.

point is you can not really make this option brand specific.
the code to create datasets is generic (and for obvious reasons should be)
and thus lives in zoneadm.c:install_func() and is executed prior calling the 
brand specific install_func().

so one can only special case this in zoneadm.c:install_func() itself
and remove the mentioning of this option from zoneadm.c and put
it into the native brands sw_support.c:install_usage() func.

however I've been asking around people that use zones pretty much since
Solaris 10 came out the door, they do not even know about that option.

also I think it would be a reasonable thing to just always have datasets for
zoneroots created going forward in terms of managability and usage.
it's not applicable to UFS zoneroots and neither to all the other brands
except the native brand, which we're not going to use much anymore
going forward with the ipkg brand.

so may I ask for a positive vote to bury that thing rather then
attempting handstands ? that'd be marvellous...


It is always possible to agglutinate multiple separate problems
into a single complex interdependent solution.
In most cases this is a bad idea.
zones-discuss mailing list

Reply via email to