From owner-freebsd-questions@freebsd.org Wed Mar 21 20:16:19 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 68C78F6363B for ; Wed, 21 Mar 2018 20:16:19 +0000 (UTC) (envelope-from mail@ozzmosis.com) Received: from homiemail-a43.g.dreamhost.com (sub5.mail.dreamhost.com [208.113.200.129]) (using TLSv1.1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0776E85AA9 for ; Wed, 21 Mar 2018 20:16:18 +0000 (UTC) (envelope-from mail@ozzmosis.com) Received: from homiemail-a43.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a43.g.dreamhost.com (Postfix) with ESMTP id AD7926003F23; Wed, 21 Mar 2018 13:16:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=ozzmosis.com; h=date:from :to:cc:subject:message-id:references:mime-version:content-type :in-reply-to; s=ozzmosis.com; bh=UCarDV5gz+KgLuoIENlR7BRln5c=; b= XXyyJcl+nRFlA9pvv3TjXxYDy45lmdSRQDfMt9fkztLNuw2do/3wv7sAPSM5gGvA 3E5hITz213Y+Yj3OO1rkbkdhqShIg2p2n7C/iwkKtS0ZlQjVuod/6YdEn90ShR8+ KEl9+kP1+LZ9k62tbYVa/yb2znEVa31jPfh28+NwsuU= Received: from blizzard.ozzmosis.com (210-84-58-210.dyn.iinet.net.au [210.84.58.210]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: relay@ozzmosis.com) by homiemail-a43.g.dreamhost.com (Postfix) with ESMTPSA id 6AD0D6003F22; Wed, 21 Mar 2018 13:16:17 -0700 (PDT) Received: by blizzard.ozzmosis.com (Postfix, from userid 1001) id A51442EC; Thu, 22 Mar 2018 07:16:14 +1100 (AEDT) Date: Thu, 22 Mar 2018 07:16:14 +1100 From: andrew clarke To: "Derek (freebsd lists)" <482254ac@razorfever.net> Cc: freebsd-questions@freebsd.org Subject: Re: freebsd-update: holding back patches, or to a specific version Message-ID: <20180321201614.j2accawaarwar6nm@ozzmosis.com> References: <50c78b4c-2832-acb2-4810-13f45794870c@razorfever.net> <44in9xf2ir.fsf@lowell-desk.lan> <391ff7b9-c340-3286-158b-20c7a2022bd0@chezmarcotte.ca> <60d4bfc4-0cd5-74b0-41e9-bfab22d66e6d@razorfever.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <60d4bfc4-0cd5-74b0-41e9-bfab22d66e6d@razorfever.net> User-Agent: NeoMutt/20180223 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Mar 2018 20:16:19 -0000 On Fri 2018-03-16 05:44:54 UTC-0400, Derek (freebsd lists) (482254ac@razorfever.net) wrote: > Yup - freebsd-update -r 11.1-RELEASE upgrade will take me to -p8, but I > *definitely* want -p7, until I can adequately assess the impact of -p8 (and > maybe let it bake for a bit). > > Any other thoughts out there? I don't think you can do what you want with freebsd-update. >From what I understand, the following in /boot/loader.conf will disable the Spectre/Meltdown mitigation code in -p8. vm.pmap.pti="0" hw.ibrs_active="0"