From owner-freebsd-questions@freebsd.org Wed Feb 1 00:46:03 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 364EBCC6576 for ; Wed, 1 Feb 2017 00:46:03 +0000 (UTC) (envelope-from yudi.tux@gmail.com) Received: from mail-io0-x235.google.com (mail-io0-x235.google.com [IPv6:2607:f8b0:4001:c06::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id F2D85A7C for ; Wed, 1 Feb 2017 00:46:02 +0000 (UTC) (envelope-from yudi.tux@gmail.com) Received: by mail-io0-x235.google.com with SMTP id l66so145616201ioi.1 for ; Tue, 31 Jan 2017 16:46:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=In9FzXfC6mg7QzMzmBgCuaOc2hrKfRyrT7K0GTSF9F8=; b=KPXuYrJdSjUD36BaXX1SmA4Q0TvRLpt1ezs3EWXV2RU08JuIC8fNL/eNVJYdFNbpOX sKG5Wclbokfs4tl3JrwWcXkggKo/m4IzmGBtqLIe8gqQ/k3xRUUq4zYMgJM306YZtaqt uNN019tYgyc4lSlHtp6W4jgQqMW4Z4Fj0gccTxawB8BPWVayHFBQD5j9kGTxX4lA6VNU DqKvJyJj0kIgnKhJzi2lOyxhJYTxcSbkYye7KbVmAF7nEhMkc0OxoOsXHVrH719RBxqb u1Q0fMD9xrhhc8hD8fOnuIZm0B85Wo7P7BCUehbYPhEAjBTmg/8fX5qNpKOpxNei/5+H QF5Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=In9FzXfC6mg7QzMzmBgCuaOc2hrKfRyrT7K0GTSF9F8=; b=tZ9K2AsEFvLYQ4y9+cqfk24f7T7e5hl/s/vriJwCao24C+EzOmcNKapHEKI1cilBF1 XMTfDOQbyUBwOh7C4YomN6g+ErouVsAXibic8Wud+Mjm9DMi4gQU3xUyuhjY+xpaFhWI aEMXBpMaDxPKG5AetwR1GcsD6VkxZPKak9/rhKOmPuDPX0WOE/dltKbfuW40gZdvcR2j AInxAvGg0MMmgeprq+QMvl3TBWEW8XCWc+QOAg4YZ8gzpDx28jc2oZdXDfVF8f3kBTNM qB/Y0gtdyl7KiZrR8htNmRhjmC70zLQtv2/GeVw+2jaPfkXcBOH8V29xfYtvaWtUrZDZ M4Lg== X-Gm-Message-State: AIkVDXK2/xQykxHIZIKOG7tlkRLklVESsvujsHAOxCuWUYGouKP1G9O33fAcFr4hUe/b6kMZBkX1BivWOI0HUw== X-Received: by 10.107.181.200 with SMTP id e191mr473215iof.217.1485909962209; Tue, 31 Jan 2017 16:46:02 -0800 (PST) MIME-Version: 1.0 Received: by 10.107.133.210 with HTTP; Tue, 31 Jan 2017 16:46:01 -0800 (PST) In-Reply-To: References: <20170118065516.GA41788@slackbox.erewhon.home> From: Yudi V Date: Wed, 1 Feb 2017 11:46:01 +1100 Message-ID: Subject: Re: issues upgrading from 10.1-RELEASE to 11-RELEASE To: krad Cc: FreeBSD Questions Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Feb 2017 00:46:03 -0000 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 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 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