On Fri, 2009-10-23 at 10:06 -0400, Dave Miner wrote: > Bart Smaalders wrote: > > Following up on a thread from several months ago.... > > > > Currently, the pkg command deals rather simplistically with boot > > environments; it always creates a new boot environent when doing an > > image update or change-variant, and never does one on pkg install. We > > recently enhanced pkg install and uninstall to prevent operation on > > the live image if doing so would modify files tagged with > > reboot-needed=true. However, it would be nice if pkg(1) could be a > > little more malleable. > > > > We can add the following option to install, uninstall, image-update > > and change-variant and change-facet: > > > > --new-be=[always, if-needed, never] > > > > which would do as the names suggest: always create a new BE, create > > one only if a file tagged w/ reboot-needed is being modified or > > removed, or never create one respectively. In the latter case, the > > operation will fail if a file tagged w/ reboot-needed would be > > affected. > > > > I suggest that the default for all commands be made "if-needed". This > > would allow for a maximum of operational flexibility. This means that > > if the only update available in your current set of repositories > > impacts OpenOffice, you would not get a new boot environment during an > > image-update. Likewise, changing facets to add or remove locale > > support would not require a reboot, but modifying facets that cause > > drivers to be removed would require a reboot since that has the > > potential of preventing said reboot. > > > > Alternatively, we can leave install and uninstall the way they > > are today, with the default being --new-be=never. I would like > > to make the rest of the commands if-needed, since this will > > improve usability significantly for common operations. > > > > comments? > > > > We've said a lot about making upgrades safe and revertable in many > presentations, so I'm a little leery here, though mostly in the > image-update case. One alternative that might be more satisfactory from > both perspectives would be to have image-update, in the no reboot needed > case, default to creating a new BE out of the pre-update snapshot. The > variance in behavior depending on circumstances may be a bit confusing, > though.
If an image-update (no reboot needed) is not in danger of rendering the current boot environment unbootable, I'd prefer a pre-update snapshot and no new BE. --joanie > Do you anticipate a per-image property that could be used to control the > default behavior, rather than requiring specification of the options? > > Dave > _______________________________________________ > pkg-discuss mailing list > [email protected] > http://mail.opensolaris.org/mailman/listinfo/pkg-discuss _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
