will young wrote: > I am with you on creating a sparse zone brand that would be suitable > for TX systems. I don't think the brand should be TX specific. Rather, > it should behave the same on solaris and TX by scanning for available > services being provided from the g-z and installing anything it still > needs in its zone. I think this would entail porting global doors to > solaris to be able to have a solaris zone that could be nearly as sparse > as a TX one.
I agree in principle but there are some things about installing a labeled zone that are fundamentally different from a non labeled zone. One of the things I'd like to see if I can get working is having things like the global zone tnrhdb database automatically updated when the labeled zone is created. There are other things about labeled zones that make them different to the default sparse zones. I think that TX label zones should be different to the default sparse zones, in part because even a sparse zone is too much duplication for the differences that a TX label zone actually needs from the global zone. -- Darren J Moffat
