Frank Middleton wrote: > This gets you > > pkg:Naming a boot environment when operating on a non-live image is not > allowed. > > Why is this and is there a workaround? > > Sorry if it's been asked before but if it has, maybe my Google-fu is off > today...
When you use the --be-name argument, it assumes that you'll also be creating a new boot environment. If you're not, it'll complain this way. The second part of this is that image-update (now just "update") no longer always creates a new boot environment, but only when it has to. If it doesn't have to, and you specified --be-name, then you'll get this error. You can also specify --require-new-be to force it to create a new BE even if one wouldn't be created automatically. There's been some discussion about whether the use of --be-name should imply --require-new-be, whether --be-name should simply be ignored when a new BE wouldn't be created, or whether we should retain the current behavior of not assuming anything about the user's intent, but we've no conclusions yet. Danek _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
