Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 1 Feb 2017 11:46:01 +1100
From:      Yudi V <yudi.tux@gmail.com>
To:        krad <kraduk@gmail.com>
Cc:        FreeBSD Questions <freebsd-questions@freebsd.org>
Subject:   Re: issues upgrading from 10.1-RELEASE to 11-RELEASE
Message-ID:  <CACo--mu0h15YCmhfSf7PchqyJ_TrwVOFD=oTG6RdgL2Wc2cb1Q@mail.gmail.com>
In-Reply-To: <CALfReyf3Wp6Rg8h52PsUP4m770BHumzqa40SCnMno09hGzhCsw@mail.gmail.com>
References:  <CACo--muKxFHp__mP9_FDSPZajvW+pEuEAmCy-R4Kr8ZOdW_RLg@mail.gmail.com> <20170118065516.GA41788@slackbox.erewhon.home> <CACo--muOgy85-97mhrm0HL4i6PR+AnO4Ui2_Q=G7NhVw9REvzQ@mail.gmail.com> <CALfReyf3Wp6Rg8h52PsUP4m770BHumzqa40SCnMno09hGzhCsw@mail.gmail.com>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
Hi Krad,

I did upgrade pkg first (pkg-static install -f pkg) but it did not upgrade
all the packages as you suggest, I had to do it manually. Anyway now
everything is back to normal.

I was thinking of using boot environments and even setup the suggested
dataset hierarchy, ie:  pool/ROOT/environments, then I realised  to boot
into a different boot-environment/dataset I can just use the bootfs flag,
this only works if all the boot environments/datasets are set to
mountpoint=legacy.
I was using this method well before beadm was officially released.
 It's only two commands to remember, clone and set bootfs, so never
bothered with beadm.
This is one of the main reasons why like FreeBSD.
I was inquiring about similar functionality in btrfs and some in the
community were adamant that it is not a  critical feature so not yet
implemented (although I have read somewhere that it was possible to boot
into a cloned dataset). I completely disagree with them. I guess they never
came across a situation where there was no easy way to go back to a working
system that was borked by an upgrade.

cheers
Yudi

On Tue, Jan 31, 2017 at 11:51 PM, krad <kraduk@gmail.com> wrote:

> Its worth noting the latest version of pkg will realise there has been an
> ABI change and upgrade all the packages without having to force them. You
> can also install the compat libraries as well if you want a quick fix if
> the rebuild is complex. If you are not using boot environments look into
> them as well and see if they would be viable for you as they can save a lot
> of grief, and let you do a lot of this grunt work before the 1st reboot.
>
> On 19 January 2017 at 16:36, Yudi V <yudi.tux@gmail.com> wrote:
>
>> Thanks guys the issue is I missed the below section as I followed the
>> release notes instructions.
>> 23.2.3.2. Upgrading Packages After a Major Version Upgrade
>>
>> ran
>>
>> pkg-static install -f pkg
>> # pkg-static upgrade -f
>>
>>
>> fixed all the issues. Problem was to do with different ABIs.
>>
>> --
>> Kind regards,
>> Yudi
>> _______________________________________________
>> freebsd-questions@freebsd.org mailing list
>> https://lists.freebsd.org/mailman/listinfo/freebsd-questions
>> To unsubscribe, send any mail to "freebsd-questions-unsubscribe
>> @freebsd.org"
>>
>
>


-- 
Kind regards,
Yudi



Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?CACo--mu0h15YCmhfSf7PchqyJ_TrwVOFD=oTG6RdgL2Wc2cb1Q>