From owner-freebsd-cloud@freebsd.org Wed Feb 10 01:59:35 2016 Return-Path: Delivered-To: freebsd-cloud@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 7D9F9AA3C35 for ; Wed, 10 Feb 2016 01:59:35 +0000 (UTC) (envelope-from rj@obsigna.com) Received: from mo6-p00-ob.smtp.rzone.de (mo6-p00-ob.smtp.rzone.de [IPv6:2a01:238:20a:202:5300::7]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.smtp.rzone.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1E5431076 for ; Wed, 10 Feb 2016 01:59:34 +0000 (UTC) (envelope-from rj@obsigna.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1455069571; l=1021; s=domk; d=obsigna.com; h=Mime-Version:To:Date:Subject:Content-Transfer-Encoding:Content-Type: From; bh=Wr+0Rbs9K+zbn04+iVH191MQZ1tvYZFJBLUgjDRxOwA=; b=Ckmxyoux2WoPJKrJ/oIDpqjcSPg5sGkBMC69qmnfP9m1FSidvagmU2Z5Ak6brW1DkIv zYc0xFTLCUgn4rKITU+IoRSdLRJGyCQXtnR1DX0t/9YJAPwbD2kisEsSeABts2UBINeLM t4mJ4tJdorASTAHY/OQad8aUb9d0nOSJFw4= X-RZG-AUTH: :O2kGeEG7b/pS1EK7WHa0hxqKZr4lnx6UhToX1IWHkW4X7v2ImaU2CVqpyLmhQrgx3Ci16w== X-RZG-CLASS-ID: mo00 Received: from mail.obsigna.com (b1504ef0.virtua.com.br [177.80.78.240]) by smtp.strato.de (RZmta 37.18 DYNA|AUTH) with ESMTPSA id h0750bs1A1xU3GK (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (curve secp521r1 with 521 ECDH bits, eq. 15360 bits RSA)) (Client did not present a certificate) for ; Wed, 10 Feb 2016 02:59:30 +0100 (CET) Received: from rolf.projectworld.net (rolf.projectworld.net [192.168.222.5]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.obsigna.com (Postfix) with ESMTPSA id 9AF1975900 for ; Tue, 9 Feb 2016 23:59:27 -0200 (BRST) From: "Dr. Rolf Jansen" Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: What is the best method to keep FreeBSD on AWS-EC2 up to date? Message-Id: Date: Tue, 9 Feb 2016 23:59:27 -0200 To: freebsd-cloud@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\)) X-Mailer: Apple Mail (2.3112) X-BeenThere: freebsd-cloud@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "FreeBSD on cloud platforms \(EC2, GCE, Azure, etc.\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Feb 2016 01:59:35 -0000 Hello! I did a trial setup on AWS-EC2 using the FreeBSD 10.2 AMI by Colin = Percival from the AWS Marketplace. The installation went smooth by a few = clicks, and everything is running fine for now. However, I got some = doubts about the correct updating path, because the usage instructions = of the AMI descriptions state: > =E2=80=A6 =46rom there on, standard FreeBSD usage and system = configuration applies, except that freebsd-update cannot be used (due to = local patches needed for the FreeBSD/EC2 platform). When I cannot use freebsd-update, what else should I do to keep the = system updated? The AMI got FreeBSD Release 10.2-p12. I am mostly concerned about the = upcoming next patch levels. I guess, when it comes to a system upgrade, = it would be best to create a new clean instance with the new system, get = my stuff over and terminate the old instance. I only don't want to do = this for every security patch.=20 Many thanks in advance for your ideas. Best regards Rolf=