For 2: I've been using a list of incorporation as a pkg -R command for installing specific versions; and putting some beadm commands around that. I can't recall where I saw the pkg list at, I think it was someone-else's comment in one of the forums, as a workaround with image-update.
This involves manually creating a BE; it may help point 1 as well as 2. I don't know, that's not what I was using it for. If you regularly change between two BE's; you might want to set up some of your service log/data direcotries (apache/postgres/??) to be a seperate filesystem from the boot environment, so that the service stays consistent. I haven't ever tried using IPS to do a version rollback though; I have no idea if that would work. (i.e. if you are on 151a7 now; I don't know if you could create a 151a4 BE) This still doesn't limit all packages to that release; but most of them are the desired release. BE=?? ##Name for boot environment, no spaces SNV=?? ##151a4 = 151.1.4 beadm create $BE beadm mount $BE /new_$SNV pkg -R /new_$SNV install -v \ pkg:/[email protected],5.11-0.$SNV \ pkg:/consolidation/cde/[email protected],5.11-0.$SNV \ pkg:/consolidation/gfx/[email protected],5.11-0.$SNV \ pkg:/consolidation/jdmk/[email protected],5.11-0.$SNV \ pkg:/consolidation/sic_team/[email protected],5.11-0.$SNV \ pkg:/consolidation/cacao/[email protected],5.11-0.$SNV \ pkg:/consolidation/cns/[email protected],5.11-0.$SNV \ pkg:/consolidation/l10n/[email protected],5.11-0.$SNV \ pkg:/consolidation/xvm/[email protected],5.11-0.$SNV \ pkg:/consolidation/dbtg/[email protected],5.11-0.$SNV \ pkg:/consolidation/ub_javavm/[email protected],5.11-0.$SNV \ pkg:/consolidation/gnome_l10n/[email protected],5.11-0.$SNV \ pkg:/consolidation/sfw/[email protected],5.11-0.$SNV \ pkg:/consolidation/hcts/[email protected],5.11-0.$SNV \ pkg:/consolidation/man/[email protected],5.11-0.$SNV \ pkg:/consolidation/sunpro/[email protected],5.11-0.$SNV \ pkg:/consolidation/gnome/[email protected],5.11-0.$SNV \ pkg:/consolidation/admin/[email protected],5.11-0.$SNV \ pkg:/consolidation/SunVTS/[email protected],5.11-0.$SNV \ pkg:/consolidation/nspg/[email protected],5.11-0.$SNV \ pkg:/consolidation/nvidia/[email protected],5.11-0.$SNV \ pkg:/consolidation/osnet/[email protected],5.11-0.$SNV \ pkg:/consolidation/solaris_re/[email protected],5.11-0.$SNV \ pkg:/consolidation/install/[email protected],5.11-0.$SNV \ pkg:/consolidation/X/[email protected],5.11-0.$SNV \ pkg:/consolidation/vpanels/[email protected],5.11-0.$SNV \ pkg:/consolidation/ips/[email protected],5.11-0.$SNV \ bootadm update-archive -R /new_$SNV beadm umount $BE beadm activate $BE -Lucas Van Tol > Date: Thu, 11 Oct 2012 05:47:36 -0700 > From: [email protected] > To: [email protected] > Subject: Re: [OpenIndiana-discuss] making new fresh install BE with pkg/IPS, > install specific OI build - ZFS feature flags compatibility > > I'd like to suggest documenting the answers that you get on the wiki. It > will make it easier for you and others to find in the future. > > --- On Thu, 10/11/12, Nikola M <[email protected]> wrote: > > > From: Nikola M <[email protected]> > > Subject: [OpenIndiana-discuss] making new fresh install BE with pkg/IPS, > > install specific OI build - ZFS feature flags compatibility > > To: "Discussion list for OpenIndiana" <[email protected]> > > Date: Thursday, October 11, 2012, 4:08 AM > > Hi, I would like to as a question > > that was probably asked many times before, > > but it would be nice to have it here for further reference. > > > > 1. Issuing what beadm and pkg (IPS) commands, > > one can make new BE (Boot environment) with fresh install > > (entire) of > > the operating system, > > that can boot independently of already running BE? > > I think that is something like making new BE with beadm, > > mounting it to > > /tmp with beadm and installing all packages that new install > > is > > consisted of to that new BE. > > > > 2. Updating to the specific /dev build of Openindiana. > > Thing I have in mind is that I > > would like to have a version before > > supporting ZFS pool feature flags, > > for possible compatibility. > > > > If older systems and those who still does not support > > feature flags, > > recognize FF ZFS as version 28, then it should be ok? I > > think I remember > > it is setting version on 999 or something, how does that > > affect > > At the end if everyone using ZFS > > (FreeBSD,ZfsOnLinux,ZFS-FUSE,Illumos > > distros) update to using feature flags, except Oracle > > Solaris ****, > > maybe question of compatibility is not much important? > > > > Thanks for manual, response and corrections :) > > > > > > > > _______________________________________________ > > OpenIndiana-discuss mailing list > > [email protected] > > http://openindiana.org/mailman/listinfo/openindiana-discuss > > > > _______________________________________________ > OpenIndiana-discuss mailing list > [email protected] > http://openindiana.org/mailman/listinfo/openindiana-discuss _______________________________________________ OpenIndiana-discuss mailing list [email protected] http://openindiana.org/mailman/listinfo/openindiana-discuss
